- From: Google <sysbot+gh@w3.org>
- Date: Sat, 16 Jun 2018 00:15:15 +0000
- To: public-secondscreen@w3.org
@tidoust That's a good point. The consequences of prohibited navigation should be described more specifically. By "not defined in terms of HTML5" I believe it's because there's no flag in the HTML5 spec that prohibits a top level browsing context from navigating itself, so we have to add a rule on top of the navigation spec to enforce this. I feel it is probably more developer friendly to abort the navigation than to close the presentation; there's no privacy downside, and it will be easier for developers to debug that way. >From an implementation point of view somewhat more complicated to do things that way, however. -- GitHub Notification of comment by mfoltzgoogle Please view or discuss this issue at https://github.com/w3c/presentation-api/issues/449#issuecomment-397771514 using your GitHub account
Received on Saturday, 16 June 2018 00:15:22 UTC