- From: Mark Foltz via GitHub <sysbot+gh@w3.org>
- Date: Thu, 11 Feb 2016 19:00:04 +0000
- To: public-secondscreen@w3.org
Thanks @tidoust for the feedback! > The procedure could still mention them as examples: I went ahead and updated this text as suggested. It's an improvement as I don't want to try to replace or amend the HTML5 spec around unloading. :) > In the case where the receiving user agent closes the presentation at user request, couldn't there valid cases where the user agent may want to terminated the presentation but not unload the document? In my mind "terminate" means that effectively the presentation no longer exists therefore and cannot accept new connections. Without the unloading requirement, the controller won't have any way of ensuring the presentation stops doing what it's doing (playing a video, etc.). I could imagine a button in the browser (or on a remote control for the display) that says "disconnect", versus "terminate." I think if this use case is important to support, we would write a separate algorithm to "disconnect a presentation" which would close all open connections, and fire a `PresentationConnectionCloseEvent` in the controlling context(s) instead of a `terminate` event. Do you mind filing a separate issue with tag "enhancement" with this idea? -- GitHub Notification of comment by mfoltzgoogle Please view or discuss this issue at https://github.com/w3c/presentation-api/pull/263#issuecomment-183010729 using your GitHub account
Received on Thursday, 11 February 2016 19:00:06 UTC