- From: François Daoust via GitHub <sysbot+gh@w3.org>
- Date: Thu, 11 Feb 2016 10:01:23 +0000
- To: public-secondscreen@w3.org
I think that the "unload a document in response to a request to navigate" circumstance should be generalized to "unload a document". This will also catch other circumstances that unload the document, e.g. reloading the page. Also, I think that you can drop the `window.close()` circumstance and the bits that call out navigating the context and navigating among fragment identifiers. Procedures defined in HTML5 ensure that calling `window.close()` or navigating the context will unload the document, except when the navigation boils down to scrolling to a fragment identifier, so these cases don't have to be called out in the Presentation API: https://www.w3.org/TR/html5/browsers.html#dom-window-close https://www.w3.org/TR/html5/browsers.html#navigate https://www.w3.org/TR/html5/browsers.html#scroll-to-fragid The procedure could still mention them as examples: ```html <li>The <a>receiving user agent</a> is to <a>unload a document</a> corresponding to the <a>receiving browsing context</a>, e.g. in response to a call to <code>window.close()</code> in the <a>top-level browsing context</a> or to a request to <a>navigate</a> that context to a new resource.</li> ``` ... perhaps completed with something like: ```html <p class="note">Navigating to a fragment identifier within the same document does not cause the document to <a data-lt="unload a document">unload</a>.</p> ``` 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? For instance, the receiving user agent could offer an option to drop all controllers from the current presentation, effectively turning the presentation back to a regular page (only useful provided some user interaction is possible on the receiving end, of course). Or do we want to prevent that possibility on purpose? In other words, I would leave unloading the document up to the receiving user agent in that case, and replace the paragraph that starts with "In any of these cases", by: ```html <p>In addition, when a <a>receiving user agent</a> receives a signal from a <a>controlling user agent</a> via the algorithm to <a data-lt="terminate-algorithm-controlling">terminate a presentation in a controlling browsing context</a> that the presentation should be terminated, it MUST <a>unload a document</a> corresponding to the <a>receiving browsing context</a>. </p> ``` -- GitHub Notification of comment by tidoust Please view or discuss this issue at https://github.com/w3c/presentation-api/pull/263#issuecomment-182788766 using your GitHub account
Received on Thursday, 11 February 2016 10:01:25 UTC