Closed
Bug 473262
Opened 16 years ago
Closed 16 years ago
"ASSERTION: not doing IDispatch, how'd this happen?" with XPCNativeWrapper(Components.interfaces)
Categories
(Core :: XPConnect, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: jruderman, Assigned: mrbkap)
Details
(Keywords: assertion, testcase)
Attachments
(2 files)
|
112 bytes,
text/html
|
Details | |
|
1.20 KB,
patch
|
jst
:
review+
jst
:
superreview+
|
Details | Diff | Splinter Review |
###!!! ASSERTION: not doing IDispatch, how'd this happen?: 'member', file /Users/jruderman/central/js/src/xpconnect/src/XPCWrapper.cpp, line 653
|
Assignee | |
Comment 1•16 years ago
|
||
We resolve xpcwrappednative.nsInterface to an interface, but no member. I don't know why we do this or how it's used, but there you go.
Assignee: nobody → mrbkap
Status: NEW → ASSIGNED
Attachment #368437 -
Flags: superreview?(jst)
Attachment #368437 -
Flags: review?(jst)
|
||
Comment 2•16 years ago
|
||
Comment on attachment 368437 [details] [diff] [review]
Proposed fix
This is due to xpconnect exposing implemented interfaces by their name as properties on wrapped natives I bet. r+sr=jst
Attachment #368437 -
Flags: superreview?(jst)
Attachment #368437 -
Flags: superreview+
Attachment #368437 -
Flags: review?(jst)
Attachment #368437 -
Flags: review+
|
|
Assignee | |
Comment 3•16 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•