Closed
Bug 396055
Opened 18 years ago
Closed 13 years ago
No scriptable IO object in JS components
Categories
(Core :: XPCOM, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: bzbarsky, Unassigned)
References
Details
The scriptable IO global object set up in bug 380813 is apparently only set up in browser chrome windows. It doesn't seem to be present in JS components, which significantly reduces the utility of the API.
This might be in the wrong component (as in, the fix might need to be on the DOM/XPConnect end of things).
Flags: blocking1.9?
Comment 1•18 years ago
|
||
This isn't limited to Scriptable IO. No "JavaScript Global Property" type objects appear in JS components.
The workaround was mentioned in bug 380813 comment 7:
https://bugzilla.mozilla.org/show_bug.cgi?id=380813#c7
| Reporter | ||
Comment 2•18 years ago
|
||
> No "JavaScript Global Property" type objects appear in JS components.
Perhaps that's what should be fixed in general?
> The workaround was mentioned
Sure, but that contract is non-discoverable (not documented anywhere, not in any place where one could expect to find it, etc).
Comment 3•18 years ago
|
||
Documentation is on my list of things which I've started yet haven't finished but still need to do for 1.9.
Comment 4•18 years ago
|
||
We've lived with similar issues (with XMLHttpRequest and others) for a while; can't block on this.
Flags: blocking1.9? → blocking1.9-
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•