- From: François Daoust via GitHub <sysbot+gh@w3.org>
- Date: Tue, 08 Sep 2015 15:06:24 +0000
- To: public-secondscreen@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 precisely. 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 See https://github.com/w3c/presentation-api/pull/186#issuecomment-138594677
Received on Tuesday, 8 September 2015 15:06:26 UTC