Closed
Bug 652610
Opened 13 years ago
Closed 13 years ago
Allow nsIDOMGlobalPropertyInitializer to parent a property under window.navigator
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
DUPLICATE
of bug 641552
People
(Reporter: ddahl, Unassigned)
Details
It would be very handy if an nsIDOMGlobalPropertyInitializer could provide a property like "navigator" and the new nsIDOMGlobalProperty would become a child of navigator automatically. I'm not sure how involved this would be, or how difficult it might be to create a property under window.navigator.
Comment 1•13 years ago
|
||
if I am reading this correctly, i think it would have made orientation, geo, desktop notifications, and upcoming permissions a bit easier to implement
Reporter | ||
Comment 2•13 years ago
|
||
(In reply to comment #1) > if I am reading this correctly, i think it would have made orientation, geo, > desktop notifications, and upcoming permissions a bit easier to implement yeah, just add a property like { // nsIDOMGlobalPropertyInitializer parent: "navigator" } and presto, you get a navigator object
Reporter | ||
Updated•13 years ago
|
Reporter | ||
Comment 3•13 years ago
|
||
According to jst, this is a bit of non-trivial work, via irc: <jst> bug 652610 would take a bit of work, we'd need a new category, and the appropriate hooks etc on the navigator to initialize the new component etc when the right name is resolved
Comment 4•13 years ago
|
||
Dupe of bug 641552?
Comment 5•13 years ago
|
||
Yup, duping. And while this might not be trivial, it's not particularly hard either. Let's sort that out in bug 641552.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•