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)
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
status1.9.2 | --- | .4-fixed |
People
(Reporter: Dolske, Assigned: mrbkap)
References
Details
(Whiteboard: [fixed-lorentz])
Attachments
(1 file)
922 bytes,
patch
|
smaug
:
review+
|
Details | Diff | Splinter Review |
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.
Assignee | ||
Comment 1•14 years ago
|
||
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 2•14 years ago
|
||
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+
Assignee | ||
Comment 3•14 years ago
|
||
http://hg.mozilla.org/mozilla-central/rev/500068ba0693
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Comment 4•14 years ago
|
||
http://hg.mozilla.org/projects/firefox-lorentz/rev/79396e021cb2
Whiteboard: [fixed-lorentz]
Comment 5•14 years ago
|
||
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
Comment 6•14 years ago
|
||
Merged into 1.9.2 at http://hg.mozilla.org/releases/mozilla-1.9.2/rev/84ba4d805430
status1.9.2:
--- → .4-fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•