WoW 2.4.0 - Interface Action failed messages

Hey folks!

With patch 2.3.2 we made some changes to help minimize unintentional propagation of taint. Since these changes resolved many of the issues presented in this thread's predecessor, we're starting a new one to track issues that have arisen with this patch.

If you get a message that states an "Interface action failed because of an AddOn", it means that an AddOn interfered with the Blizzard UI in some way.

PLEASE CHECK FOR AN UPDATED ADDON, AS YOUR PROBLEM MAY ALREADY BE RESOLVED!

If it still happens, you can diagnose what's going on and let the author know...

To diagnose this, enter the following into chat "/console taintLog 1" and restart the game and try to reproduce it. If you reproduce it, you can quit the game and search through the file Logs\taint.log for the word "blocked". Once you have done this you can turn off logging by entering the following into chat "/console taintLog 0".

Please use this thread to post links to your taint.log file if you get this message.

You'll only get the "blocked" messages in combat, so the easiest way to test this is to go to a low level zone and let a weak creature attack you while you do things involving targeting, group changes, pet changes, etc.

Remember, taint by itself is fine, it only becomes a problem if it results in a "blocked" message.

The previous post can be found here:

http://forums.worldofwarcraft.com/thread.html?topicId=2518903044&sid=1

Thanks!
--Zootfizzle

Q u o t e:
Not sure if it's intentional, but calling ReloadUI() from an OnMouseDown handler causes a taint fault, where calling it from an OnClick handler does not.

Can you post a link to a minimal example?

Thanks!

Q u o t e:

Sure thing!
http://evilempireguild.org/ui/tainttest.zip

Oh right, this is not a bug. ReloadUI() can only be called from an "input" event, which clicks are, but mouse button presses are not (for arcane reasons)

Thanks!

This is fixed for 2.4.2, BTW.