Re: [sensors] Simplify extension of the Permissions API for concrete sensor implementations

> require spec editors to get a change in the Permission API for every
 new spec they write?

I hate to say it, but this one :( It's the least worst. 

I don't want a DOMString because in Gecko we generate all the bindings
 from the WebIDL - so not having them in an enum is a pain for us (or 
we will make a fake enum... but then we might get funky behavior)... 
the spec will have to treat the DOMString like it's an enum, which 
would be redundant. 

Worst case, we have the permission enum in its own spec/wiki/register 
- where people have to register their keys (including the Permissions 
API).    


-- 
GitHub Notif of comment by marcoscaceres
See https://github.com/w3c/sensors/issues/22#issuecomment-110951642

Received on Thursday, 11 June 2015 00:03:43 UTC