- From: François Daoust via GitHub <sysbot+gh@w3.org>
- Date: Wed, 16 Sep 2015 09:51:05 +0000
- To: public-secondscreen@w3.org
I note some feedback from the TAG on the lifetime of a presentation: [[ 3.The concept of connecting to a shared session object had parallels to the SharedWorker object. The SharedWorker is established by the first party making a connection to it, then it becomes available to any requesting parties, provided they are within the same-origin. It's lifetime terminates when the last document connected to it terminates. In the Presentation API, the spawned presentation browsing context has a lifetime that is potentially longer-lived than the SharedWorker meaning that if no existing connection calls the session's stop() API it could potentially live indefinately. This could become a problem as it leaves the lifetime of a presentation explicitly up to well-behaved JavaScript management. In the web platform, we'd generally like to avoid these type of mananagement problems, espeically when the "second screen" may not have a user-interaction input modality. ]] https://github.com/w3ctag/spec-reviews/blob/master/2015/presentation-api.md -- GitHub Notif of comment by tidoust See https://github.com/w3c/presentation-api/issues/35#issuecomment-140691397
Received on Wednesday, 16 September 2015 09:51:10 UTC