Re: [presentation-api] Defines two conformance classes for the specification

@tidoust Thanks for all the comments.  I went ahead and merged the two
 interfaces and use prose to make statements about each property of 
the interface as you suggested.

We may want to also make statements to the effect that a 
non-controlling UA must not define 
`navigator.presentation.defaultRequest` and a non-receiving UA must 
not define `navigator.presentation.receiver`.  But I am not sure.

I am going to merge this, feel free to make additional 
suggestions/PRs.


-- 
GitHub Notif of comment by mfoltzgoogle
See 
https://github.com/w3c/presentation-api/pull/204#issuecomment-146969374

Received on Friday, 9 October 2015 19:37:57 UTC