Closed
Bug 965715
Opened 11 years ago
Closed 11 years ago
[regression] JavaScript-global-constructor object has no interface
Categories
(Core :: XPConnect, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: j, Unassigned)
References
Details
Attachments
(1 file)
2.18 KB,
application/x-xpinstall
|
Details |
Objects created via JavaScript-global-constructor by an add-on no longer
have the interface defined via QueryInterface: XPCOMUtils.generateQI(..).
This started happening in recent Nightlies.
Last stable release (26) still exposes the interface as expected.
Comment 1•11 years ago
|
||
Jan, could you post an example testcase (small addon that easily shows the problem)?
Or alternately, would you be willing to find the first nightly that changed the behavior?
Flags: needinfo?(j)
Reporter | ||
Comment 2•11 years ago
|
||
Source of extension can also be found at:
http://r-w-x.org/?p=jsglobal.git;a=summary
example use that fails in nightly:
g = new JsGlobal();
console.log('g.foo', g.foo);
console.log('g.bar()', g.bar());
Flags: needinfo?(j)
Comment 3•11 years ago
|
||
Jan, thanks!
It looks like the issue you're having is that nsISecurityCheckedComponent has been removed. See bug 794943. So Ci.nsISecurityCheckedComponent in your component is undefined and things go south.
I tried just removing the nsISecurityCheckedComponent bits and everything _seems_ to work after that... Bobby, is that expected?
Blocks: 794943
Flags: needinfo?(bobbyholley)
Comment 4•11 years ago
|
||
Oh, I see. There's an nsIClassInfo with DOM_OBJECT set. So the nsISecurityCheckedComponent bits are just superfluous.
Updated•11 years ago
|
Flags: needinfo?(bobbyholley)
Comment 5•11 years ago
|
||
We're not going to reintroduce nsISecurityCheckedComponent, so wontfix, I guess, but fixing the addon in this case should be pretty simple.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
Comment 6•11 years ago
|
||
(In reply to Boris Zbarsky [:bz] from comment #5)
> fixing the addon in this case should be pretty simple.
Note that in this case, fixing the addon should just involve removing the references to nsISecurityCheckedComponent, since the addon also implements nsIClassInfo, and flags itself as DOM_OBJECT.
Reporter | ||
Comment 7•11 years ago
|
||
Thanks, removing nsISecurityCheckedComponent and related code indeed fixes Firefogg.
I remember this was needed at some point to pass File objects,
but always great if removing code can fix things.
You need to log in
before you can comment on or make changes to this bug.
Description
•