W3C home > Mailing lists > Public > public-secondscreen@w3.org > August 2016

Re: [presentation-api] Clarify the default presentation request mechanism?

From: François Daoust via GitHub <sysbot+gh@w3.org>
Date: Mon, 29 Aug 2016 09:32:34 +0000
To: public-secondscreen@w3.org
Message-ID: <issue_comment.created-243078171-1472463152-sysbot+gh@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 
 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 
 do not contain the `receiver` definition and the [IDL test that check
 receiving user 
 do not contain the `defaultRequest`.

GitHub Notification of comment by tidoust
Please view or discuss this issue at 
 using your GitHub account
Received on Monday, 29 August 2016 09:32:42 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:19:01 UTC