W3C home > Mailing lists > Public > public-secondscreen@w3.org > June 2018

[presentation-api] Clarify behavior when the receiving page attempts to navigate itself

From: François Daoust via GitHub <sysbot+gh@w3.org>
Date: Tue, 19 Jun 2018 08:35:21 +0000
To: public-secondscreen@w3.org
Message-ID: <issues.opened-333571194-1529397320-sysbot+gh@w3.org>
tidoust has just created a new issue for https://github.com/w3c/presentation-api:

== Clarify behavior when the receiving page attempts to navigate itself ==
Issue initially raised in https://github.com/w3c/presentation-api/issues/449#issuecomment-397597655

In [6.6.1](https://w3c.github.io/presentation-api/#creating-a-receiving-browsing-context), the Presentation API spec says that, in receiving contexts, "The top-level browsing context MUST NOT be allowed to navigate itself", but it does not explain what is to happen if it attempts to do so.

Two main possibilities:
1. Abort with a `SecurityError`.
2. Close the receiving browsing context.

We should probably be doing 1. (see https://github.com/w3c/presentation-api/issues/449#issuecomment-397771514): it is consistent with the [navigate](https://www.w3.org/TR/html53/browsers.html#navigated) algorithm in HTML when the context is not "allowed to navigate" and is developer-friendly since it allows them to debug the situation. Problem is it is harder to implement and it does not match what Chrome is currently doing. Second possibility matches how Chrome currently behaves, is easier to implement, but makes it harder for developers to debug and is not consistent with the usual navigation algorithm.

Please view or discuss this issue at https://github.com/w3c/presentation-api/issues/455 using your GitHub account
Received on Tuesday, 19 June 2018 08:35:31 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 19 June 2018 08:35:32 UTC