[presentation-api] Behavior of window.reload() on presentation receiver page

mfoltzgoogle has just created a new issue for https://github.com/w3c/presentation-api:

== Behavior of window.reload() on presentation receiver page ==
Internally, a developer noted that calling `window.location.reload()` on a presentation receiver page in Chrome closes the page.  (Chrome closes presentations that attempt to navigate.) 

The spec isn't explicit about how browsers should behave in this situation.

- Is there a use case for allowing presentations to `reload()`?  It would be simpler not to allow it, as we don't have steps to restore any PresentationConnections after reload.
- If it's not allowed, then this might deserve a small spec update to be explicit about the this case.



Please view or discuss this issue at https://github.com/w3c/presentation-api/issues/449 using your GitHub account

Received on Monday, 7 May 2018 23:03:00 UTC