Re: partial interfaces, [NoInterfaceObject]

On 2/13/14 11:50 AM, Michael van Ouwerkerk wrote:
> This change seems to make sense as it is less verbose, and there's no
> need for multiple interfaces to implement this. Is there any further
> guidance on pros and cons?

I think that sums it up.  You should probably use partial interface if 
you can.  The only time you need "implements" is if you have multiple 
interfaces that all want to share the same IDL snippet.

The only reason to consider "implements" here, I suspect, is if we plan 
to have .geolocation on WorkerNavigator.  And even then, two separate 
partial interfaces might be clearer.

> What are the reasons for exposing an
> object like this in the global namespace?

Mostly it allows scripts to easily get to Geolocation.prototype without 
jumping though weird hoops.

That's of somewhat limited utility in the case of singleton objects like 
this one, of course...


Received on Thursday, 13 February 2014 17:03:16 UTC