023

BazMap

023 (2026-05-03)

Full Changelog Previous Releases

• BazMap v023 - Fix SetPropagateMouseClicks taint on WorldMap toggle. The user reported ADDON_ACTION_BLOCKED for Frame:SetPropagateMouseClicks() blamed on BazMap when opening the WorldMap (TOGGLEWORLDMAP keybind). Trace: ToggleWorldMap > QuestLogOwnerMixin:HandleUserActionToggleSelf > SetDisplayState > ShowUIPanel > Blizzard_MapCanvas:RefreshAllData (called via secureexecuterange across all data providers) > DelveEntranceDataProvider:RefreshAllData > AreaPOIDataProvider > AcquirePin > SharedMapPoiTemplates SuperTrackablePinMixin:OnAcquired > UpdateMousePropagation > self:SetPropagateMouseClicks(...) - blocked. Same root cause as the v014 POI-tooltip taint fix: BazMap calls SetAttribute on WorldMapFrame's UIPanelLayout-area / UIPanelLayout-enabled / UIPanelLayout-allowOtherPanels (required to detach from Blizzard's panel layout system so the map can be freely positioned and scaled - documented as unavoidable in the file's header comment block). The taint propagates through the WorldMap and its child pins; once a pin is tainted, any subsequent secure-restricted call inherits the taint and gets blocked. SetPropagateMouseClicks is one such call. Same fix as v014: wrap the offending mixin method in pcall so the error is swallowed silently. SuperTrackablePinMixin.UpdateMousePropagation is overridden at file-scope with a pcall wrapper around the original. The pin loses the correct mouse-pass-through configuration for the affected frame (a click on the pin may or may not also pass through to the map underneath), which is a minor UX degradation - clicking IS still functional, just the propagation behaviour might not match what Blizzard intended for that specific pin's super-track state. The map and all other pins continue to work normally. The wrap is install at file scope so it's in place before any data provider refresh fires, which can happen as early as PLAYER_ENTERING_WORLD on a /reload. Bump to 023