- From: Mark Foltz via GitHub <sysbot+gh@w3.org>
- Date: Tue, 12 Jan 2016 00:35:38 +0000
- To: public-secondscreen@w3.org
mfoltzgoogle has just submitted a new pull request for https://github.com/w3c/presentation-api: == Updated version of PR #238 == This is based on PR #238 but somewhat simplifies the two parts of the close algorithm and how they are invoked. The first part signals the destination browsing context that the connection is closing and passes the reason (close or wentaway). The second part queues a task to change the connection state and fire the close event. I wonder if we should change state before queueing a task on the event loop to avoid re-entrancy, to ensure correct behavior when calling close() then close() again (or another API method that checks the PresentationConnection state). See https://github.com/w3c/presentation-api/pull/239
Received on Tuesday, 12 January 2016 00:35:42 UTC