WowAce

What steps will reproduce the problem?
1. Right clicking a user in a BG and clicking report away will cause an error indicating the function can only be done via the Blizzard UI.
2. Right clicking the BG "eye" icon around the mini map and selecting Leave queue will cause the same error that the function can only be done via the Blizzard UI (this is new I believe as of the latest 3.6.20 Beta 2).

What is the expected output? What do you see instead?
1. Player should be reported away.
2. I should be removed from the BG queue.

What version of the product are you using?
3.6.20 Beta 2

Do you have an error log of what happened?

Please provide any additional information below.
I've been using Xperl for years. Fantastic add-on!! :-)

I will investigate into this issue

I can be removed from the bg queue, this is not an XPerl problem. However you can't report player AFK, I suspect they made a restriction similar to Set Focus one. Here's the full error report:

1x [ADDON_ACTION_FORBIDDEN] AddOn "* TaintForced *" tried to call the protected function "ReportPlayerIsPVPAFK()". !BugGrabber-r188\BugGrabber.lua:587: in function <!BugGrabber\BugGrabber.lua:587> <in C code> FrameXML\UnitPopup.lua:1658: in function "func" FrameXML\UIDropDownMenu.lua:710: in function "UIDropDownMenuButton_OnClick" <string>:"*:OnClick":1: in function <string>:"*:OnClick":1

Locals: nil

Thanks for the update! I just tried removing myself from a BG queue again and it's working again. Must have been a fluke or some other add-on update. So yeah, just the AFK issue in the BGs remains.

Hate that stupid dropmenu taints, so Blizzard want to fix them on Patch 5.2, GREAT!

I have enough with all such TaintForced Error bullshit, even not all of them will be fixed. :p

On battle.net forums it has been said that someone was abusing that function so they made it protected in 5.1

@Asixandur: Go

The problem is, when it get protected, always fucked many 3rd party addons up and Blizzard don't really care/or want authors using their buggy methods that not 100% fixed.

So, based on what PlayerLin mentioned...are we looking at patch 5.2 before a fix can be implemented?

@Clomane77: Go

I'm currently waiting for API changes in 5.2 to be loaded by someone to check if they have really changed something to fix these problems.

The PTR can using 3rd party addons? If so, someone should check it out...

@PlayerLin: Go

Try last alpha please

Can someone try that?

Still doing it with r852 | asixandur | 2013-06-16 17:17:06. I have to disable XPerl to be able to report someone afk in a battleground.

@cerobinson: Go

I'm still working on that.

It was fixed for a while, but it's back with WoW 5.4.0.17371 and XPerl 3.7.2 r854.

I know, the fix caused very small tooltips with less commands. Don't know what to do.

Sounds like that stupid SetFocus shit goes again, not possible use the same method on this one?

@PlayerLin: Go

Are you sure about that?

@Asixandur: Go

OK, not quite, setfocus/clearfocus was fixed by Blizzard, they just made that right click menu never do taint shit ever when using any of 3rd-party addons...

So, I guess someone should tell Blizzard to fix this one too...:(

@PlayerLin: Go

We're currently showing an incorrect menu for the raid frames because there's no way to tell the blizz secure code that we want to show the other one. Probably this won't ever be fixed, but I still keep it Accepted because it's true that it doesn't work as it should. However it doesn't generate any lua errors/taints at the moment.

1x [ADDON_ACTION_FORBIDDEN] AddOn "XPerl" tried to call the protected function "ReportPlayerIsPVPAFK()". !BugGrabber-r198-release\BugGrabber.lua:552: in function <!BugGrabber\BugGrabber.lua:552> <in C code> FrameXML\UnitPopup.lua:1660: in function "func" FrameXML\UIDropDownMenu.lua:730: in function "UIDropDownMenuButton_OnClick" <string>:"*:OnClick":1: in function <string>:"*:OnClick":1

Locals: nil

@cerobinson: Go

I'm not sure if it possible, but try again with all X-Perl addons loaded only(can load with bug-catching addons), but I guess you should post a new ticket since you have LUA error but...

This is very informative and i completely admire it like http://essaywritingservices-help.blogspot.com/ have also fantastic job.