- From: Jer Noble via GitHub <sysbot+gh@w3.org>
- Date: Tue, 20 Aug 2019 22:11:52 +0000
- To: public-secondscreen@w3.org
@mounir said "Instead of adding a new state, could we add information to the disconnect event that explains why the disconnection happened?" I'm not sure how that simplifies things. `"disconnected"` doesn't appear to imply that the element will attempt to reconnect when the `src` changes. Also, in the "Browser initiated remote playback" case, you'd either get a `"disconnected"` event without a matching `"connecting"` one, or no events at all, depending on your interpretation of the "Browser initiated remote playback" section. -- GitHub Notification of comment by jernoble Please view or discuss this issue at https://github.com/w3c/remote-playback/issues/125#issuecomment-523215111 using your GitHub account
Received on Tuesday, 20 August 2019 22:11:54 UTC