W3C home > Mailing lists > Public > public-secondscreen@w3.org > September 2015

Re: [presentation-api] Add PresentationReceiver and navigator.presentation.receiver to access it.

From: François Daoust via GitHub <sysbot+gh@w3.org>
Date: Tue, 08 Sep 2015 15:06:24 +0000
To: public-secondscreen@w3.org
Message-ID: <issue_comment.created-138594677-1441724783-sysbot+gh@w3.org>
@mounirlamouri Could you clarify why you want a controlling UA to 
implement PresentationReceiver? Or is it a typo in your comment?

I do not know in which order #91 and #93 should be done. I think that 
the pull request is fine provided that we keep #93 open. Once 
"presenting UA" and "controlling UA" are defined as conformance 
classes, sentences such as: "The receiver MUST return null if the 
current browsing context is not a presenting browsing context and 
return a PresentationReceiver instance otherwise" may need to be 
revisited to clarify what each type of UA needs to implement 

For instance, here, I am not clear what "typeof PresentationRequest" 
will return in a presenting-only UA. If defined, that would mean that 
the UA needs to implement the Constructor too and thus some "fake" 
logic. How would a Web app know that it's useless to offer the user 
with a "present" button in that case?

GitHub Notif of comment by tidoust
Received on Tuesday, 8 September 2015 15:06:26 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:18:58 UTC