Closed
Bug 450459
Opened 16 years ago
Closed 13 years ago
Make a top-level 'mozilla' object for content JS
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
DUPLICATE
of bug 652140
People
(Reporter: bent.mozilla, Unassigned)
Details
Make a top-level 'mozilla' object for content JS. And hang the worker thread stuff off of that rather than the navigator object.
|
||
Comment 1•16 years ago
|
||
How would this relate to the work being done to create a DOM binding for the native JSON in bug 408838?
|
||
Comment 2•16 years ago
|
||
AFAIK the JSON stuff is being exposed as global functions now, so it doesn't need a mozilla property any longer.
|
||
Comment 3•16 years ago
|
||
(In reply to comment #1)
> How would this relate to the work being done to create a DOM binding for the
> native JSON in bug 408838?
>
JST is right in comment 2, but the patch there has the IDL and nsGlobalWindow code necessary for such an object.
Given that there is a spec now workers don't need this either. So should we WONTFIX this for now?
|
Reporter | |
Comment 5•16 years ago
|
||
Removing dependency, at least.
No longer blocks: workerthreadstracker
|
||
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
|
Assignee | |
Updated•12 years ago
|
Component: DOM: Mozilla Extensions → DOM
|
|
Assignee | |
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•