When the battleground queue “pops” and the “Join/Hide” frame appears, when I click on it this error appears:
Date: 2019-12-12 16:43:52
ID: -12
Error occured in: AddOn: SlideBar
Count: 11
Message: Error: AddOn SlideBar attempted to call a forbidden function (AcceptBattlefieldPort()) from a tainted execution path.
Debug:
[C]: AcceptBattlefieldPort()
..\FrameXML\StaticPopup.lua:689: OnAccept()
..\FrameXML\StaticPopup.lua:5003: StaticPopup_OnClick()
[string "*:OnClick"]:1:
[string "*:OnClick"]:1
Locals:
None
AddOns:
I also get it with TradeSkillMaster; exact same lines.
If I disable these then I have no issue.
Slidebar’s dev team has specifically stated it isn’t on their end.
Note: I can use the minimap ‘button’ to still enter.
3 Likes
Oh, that’s not just you. I have good reason to think Slidebar is telling you how it is. It honestly seems to be on Blizzard’s end. I (& another of other people I’ve seen here) have had the exact same issue since the patch. The reason I don’t think it’s truly an addon issue: When I disable the “problem addon”…next time I go to queue, it “decides” it’s a different addon entirely. It will keep being picky until they’re all disabled. I can’t enter a BG til I disable the one it’s saying is the “culprit”. It seems pretty clear to me that something went amiss when Blizzard decided to toy with the API for whatever reason. I have a guess but…if it’s not broke don’t fix it.
I use slidebar & haven’t even gotten that error, if that helps.
TLDR; It’s not just you, it really probably is Blizzard’s end.
1 Like
Interesting. I have the exact same issue as the OP (in fact we both reported it to the SlideBar devs), although I haven’t received the error with any other addon and I run with plenty of them.
1 Like
You should still be able to enter by clicking on the button on the minimap and joining.
1 Like
Yeah, I saw that. Thanks for the heads up, I appreciate that.
I have verified in the source that SlideBar does not call that function, and I cannot find any way it could call that function. (so far, I have found zero addons that call that function!)
This appears to be another case of the Blizzard code blaming the wrong addon for an error. This really needs to be debugged on the Blizzard side of the code.
2 Likes
Same thing here. Games gives error when trying to enter BG, I disable the addon specified in the error, then the next time it’s a different addon.
1 Like
Got the same issue with another addon (Prat) and got another kind of issue which is very similar to this one, when trying to disenchant an item in my bags I have this message and can’t DE until I deactivated my addon (bagnon). Can’t say for the first one as it only happens with BG and obviously before BG were added I didn’t have the issue.
But as for the second issue I never had any issue with DE and bagnon, it just appeared with the 1.13.3 update.
Having same problem here. First Prat, then Details, and Bagnon today. Yesterday it also disabled DBM…
Just want to add my voice to the report
Getting the same type of errors… with both battleground joining and also raid frames too.
is this taint coming from the drop down system being overly picky??
I’ve done what i can to confirm this – pretty much the Blizzard UIDropDownMenu system is tainting < < EVERYTHING > >
So if you have an addon that uses it in any way, figure out other options.
interesting very nice find.
Jesus…just by the name of it, that’s pretty much every single Addon out there with a config UI…so, like, all of them. 
There are replacements available for the DropDownMenu system that should be used instead. If you find an addon that’s doing this (you have to check the code for that specific string “UIDropDownMenu” ) open a ticket/bug report with the Author.
1 Like