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

The developer could add a button to the controller to manually reconnect once the receiver page has finished reloading.

Since this use case is mostly for debugging, I'm not sure it's worth adding a new reload event to the `PresentationConnection` to signal the controller that a reload had completed and reconnection is possible.

The spec language may need adjustment to note that reloading the receiver should not terminate the presentation and the reloaded presentation retains the same id (to allow `reconnect()` to work). 


-- 
GitHub Notification of comment by mfoltzgoogle
Please view or discuss this issue at https://github.com/w3c/presentation-api/issues/449#issuecomment-387820161 using your GitHub account

Received on Wednesday, 9 May 2018 17:48:03 UTC