Re: [presentation-api] Separate interface for controlling page and presenting page

I like the idea of sticking to the `navigator.presentation` namespace.

That's more an editorial point perhaps but since we'll end up with two
 conformance classes in the spec, it seems good to have separate IDL 
for each class of products to be able to say "the controlling user 
agent MUST implement the interface defined in section X.Y." instead of
 "the controlling user agent MUST implement the `defaultRequest` 
attribute of the `Presentation` interface".

How would you define the resulting `Presentation` interface in the 
spec, @mounirlamouri ? An empty interface completed with two `partial`
 interfaces, one with `defaultRequest` and the other with `receiver`?

-- 
GitHub Notif of comment by tidoust
See 
https://github.com/w3c/presentation-api/issues/91#issuecomment-136962993

Received on Wednesday, 2 September 2015 07:40:09 UTC