- From: François Daoust via GitHub <sysbot+gh@w3.org>
- Date: Mon, 29 Aug 2016 09:32:34 +0000
- To: public-secondscreen@w3.org
I dropped "chrome" from "browser chrome" as suggested. Feel free to improve that part if needed, I don't think there's a spec that defines what that encompasses precisely. For instance, I see HTML5 talks about [browser interface elements](http://www.w3.org/TR/html51/browsers.html#browser-interface-elements) while other specs use "browser chrome" as we do (e.g. Media Capture and Streams). To avoid possible ambiguities regarding the `defaultRequest` attribute in a receiving user agent and the `receiver` attribute in a controlling user agent, I propose to simply say which class of user agents it to implement which `partial interface` of `Presentation` and to drop the sentences that refer to the other class altogether. That is what I did in my latest commit. This seems clearer to me and also better from an IDL perspective. The IDL tests that we have typically filter out the partial interface definition that does not apply to the class of user agent being tested. In other words, the [IDL tests that check controlling user agents](https://github.com/w3c/web-platform-tests/blob/master/presentation-api/controlling-ua/idlharness.html) do not contain the `receiver` definition and the [IDL test that check receiving user agents](https://github.com/w3c/web-platform-tests/blob/master/presentation-api/receiving-ua/idlharness.html) do not contain the `defaultRequest`. -- GitHub Notification of comment by tidoust Please view or discuss this issue at https://github.com/w3c/presentation-api/pull/334#issuecomment-243078171 using your GitHub account
Received on Monday, 29 August 2016 09:32:42 UTC