- From: Mark Foltz via GitHub <sysbot+gh@w3.org>
- Date: Mon, 14 Sep 2015 16:41:06 +0000
- To: public-secondscreen@w3.org
Regarding @schien's comment https://github.com/w3c/presentation-api/issues/35#issuecomment-139466798 for behavior of `terminate()` in 2-UA mode: If the controlling context calls `terminate()`, the assumption is that the controlling UA has some way of terminating the receiving browsing context, and thus knows that the presentation sessions in the controlling context should transition to `terminated.` If the receiving browsing context terminates itself, there may be signaling required to tell the controlling presentation sessions that this was an explicit termination of the presentation (and not, e.g., by a network disconnection or by powering off the display). This is addressed in L771-792 of the PR as an optional (MAY) requirement for the presenting UA. I think the PR should be updated to handle the case where the receiving context calls `window.close()` instead of `terminate().` The two functions would seem to function identically for the receiving context. -- GitHub Notif of comment by mfoltzgoogle See https://github.com/w3c/presentation-api/issues/35#issuecomment-140139652
Received on Monday, 14 September 2015 16:41:08 UTC