- From: Mark Foltz via GitHub <sysbot+gh@w3.org>
- Date: Wed, 10 Feb 2016 21:59:10 +0000
- To: public-secondscreen@w3.org
mfoltzgoogle has just submitted a new pull request for https://github.com/w3c/presentation-api: == Clarifies when and how presentations are unloaded == This addresses #18 (Define reconnection for cross-page navigation on presenting user agent) by specifically terminating the presentation when navigation is attempted (other than by fragment identifier). It also spells out the other circumstances in which a presentation is to be terminated. This list may not be comprehensive; please point out anything missing. Reading this, it looks like there are three distinct algorithms: 1. What happens when a controller terminates the presentation 2. What happens to the presentation 3. How connected controllers should respond to the terminated presentation Perhaps it would be clearer to split 2 and 3 into separate sections. Thoughts? See https://github.com/w3c/presentation-api/pull/263
Received on Wednesday, 10 February 2016 21:59:12 UTC