- From: François Daoust via GitHub <sysbot+gh@w3.org>
- Date: Mon, 01 Feb 2016 10:35:44 +0000
- To: public-secondscreen@w3.org
My recollection of the discussion we had with PING is that the focus was from a controlling browsing context perspective, and that the goal was to ensure that the user has a way to tell which origin is being presented from the chrome of the controlling user agent. I realize that, in the generic case, the controlling user agent may not be able to guarantee that the origin displayed in its chrome is the one actually presented by the receiving user agent: it needs to assume that the receiving user agent is behaving as requested. Also, the discussion on nested contexts also points out the need to show the requesting origin in the picker UI: https://github.com/w3c/presentation-api/issues/79#issuecomment-156304038 I would not add specific guidelines from a receiving browsing context perspective. I would rather treat the receiving user agent as a "regular" user agent rendering Web content. The final conclusion of #99 "Define behavior of Window and Fullscreen APIs in the presentation browsing context" could perhaps require a different approach. -- GitHub Notification of comment by tidoust Please view or discuss this issue at https://github.com/w3c/presentation-api/issues/223#issuecomment-177902959 using your GitHub account
Received on Monday, 1 February 2016 10:35:46 UTC