Changelog

1.8.0 - 2026-04-25

Refinements to chat lockdown handling

Iterating on the 1.7.0 lockdown work after live testing revealed taint propagation through Blizzard's chat editor — any addon-side SetText / SetAttribute / ChatFrame_OpenChat call taints the editor frame, so its own SendText → SendWhisper gets blocked too. The pre-fill approach was abandoned in favor of instructing the user.

• Outbound during lockdown: DIM no longer touches the default chat editor. It preserves your typed message in the DIM editbox (so you can copy it) and prints two orange lines in the tab: the lockdown notice plus the exact slash form (/w PlayerName your message) to retype into Blizzard's chat editor. That untainted path is the only one that sends during an encounter.
• Inbound secret whisper: prints a single orange [DIM] message received during boss fight line in the default chat frame (60s throttle) and plays the incoming sound. No DIM-window notice — without a known sender we can't attribute it to a tab. No flash, no minimap pulse.
• /dim testlockdown: toggles Blizzard's addonChatRestrictionsForced CVar so you can repro lockdown behavior outside of an actual encounter. IsRestrictedChatContext() checks both C_ChatInfo.InChatMessagingLockdown() and the test CVar.