Closed Bug 544544 Opened 14 years ago Closed 14 years ago

chrome event listener gets NS_ERROR_XPC_BAD_OP_ON_WN_PROTO when checking event.isTrusted

Categories

(Core :: XPConnect, defect)

x86
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED FIXED
Tracking Status
status1.9.2 --- .4-fixed

People

(Reporter: Dolske, Assigned: mrbkap)

References

Details

(Whiteboard: [fixed-lorentz])

Attachments

(1 file)

Bug 538910 adds a chrome event listener, which checks the event's .isTrusted property. But when it does this, an exception is thrown:

  uncaught exception: [Exception... "Illegal operation on WrappedNative
  prototype object"  nsresult: "0x8057000c (NS_ERROR_XPC_BAD_OP_ON_WN_PROTO)

I *think* this started happening after adding bug 541076 to my mq, maybe due to using nsIDOMDataContainerEvent or adding NS_EVENT_FLAG_ONLY_CHROME_DISPATCH? Could be coincidence, though.

mrbkap has done some initial debugging.
Attached patch PatchSplinter Review
I'm still confused as to how this works at all (how do we resolve isTrusted on the event?) but we need to make sure that DataContainerEvent advertises that it's nsIDOMEvent and nsIDOMNSEvent to XPConnect.
Attachment #425531 - Flags: review?(Olli.Pettay)
Comment on attachment 425531 [details] [diff] [review]
Patch

So far datacontainerevent has been used only by C++ a11y code, I believe.
So no one noticed this :(
Attachment #425531 - Flags: review?(Olli.Pettay) → review+
http://hg.mozilla.org/mozilla-central/rev/500068ba0693
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Blanket approval for Lorentz merge to mozilla-1.9.2
a=beltzner for 1.9.2.4 - please make sure to mark status1.9.2:.4-fixed
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: