652610 - Allow nsIDOMGlobalPropertyInitializer to parent a property under window.navigator

Status: RESOLVED DUPLICATE of bug 641552

(Core :: DOM: Core & HTML, defect)

Description

[David Dahl :ddahl]

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

[Doug Turner (:dougt)]

if I am reading this correctly, i think it would have made orientation, geo, desktop notifications, and upcoming permissions a bit easier to implement

Comment 2

[David Dahl :ddahl]

(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

Comment 3

[David Dahl :ddahl]

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

[Philipp von Weitershausen [:philikon]]

Dupe of bug 641552?

Comment 5

[Johnny Stenback (:jst)]

Yup, duping. And while this might not be trivial, it's not particularly hard either. Let's sort that out in bug 641552.