Reposting from my wowace post.
Since these forums are frequented by both EU and US addon developers maybe it will reach the all-elusive 'devs'.
The issue affects many of the addons in the beta category here
(practically any that call UIDropDownMenu_Initialize at some point)
The taint.log posted further down is quite self-explanatory if you follow the line numbers and look at the FrameXML\ files referenced.
It seems that in the recent 3.0.2 (8885) beta build any addon that calls
Code:
UIDropDownMenu_Initialize(frame, initfunc, ...)
causes action blocked errors due to taint.
Steps to reproduce:
1. Load an addon that uses UIDropDownMenu_Initialize and take whatever action is required for the function to be called
(show an options screen etc)
2. Right-click the target frame and choose "Set Focus"
Similar issues with "Clear Focus".
Both setfocus and clearfocus work without issue if you use keybinds and not the dropdown menu.
Typical taint.log contains:
Code:
Global variable UIDROPDOWNMENU_INIT_MENU tainted by _ _ _ _ _
Interface\FrameXML\UIDropDownMenu.lua:30 UIDropDownMenu_Initialize()
...
Execution tainted by _ _ _ _ _ while reading UIDROPDOWNMENU_INIT_MENU -
Interface\FrameXML\UnitPopup.lua:997 func()
...
An action was blocked because of taint from _ _ _ _ _ - FocusUnit()
Interface\FrameXML\UnitPopup.lua:1181 func()
Several addons are giving me those messages.
Those that initialize the dropdown in OnLoad handlers are blamed first.
If you go on disabling, other addons take their place after they call UIDropDownMenu_Initialize
(in OnShow handlers for example)
Haven't found a workaround sofar or a mention on UI & Macros forum so
I don't know if this is expected behavior we're supposed to circumvent somehow.
Edit: Addons in question use local variables btw (self not this) and the action blocked errors
happen regardless of combat status (both when trying to setfocus and showing dropdowns)
ie you'll get them even if you haven't entered combat at all.
Threaded Mode
