- From: François Daoust via GitHub <sysbot+gh@w3.org>
- Date: Wed, 20 Jan 2016 15:59:18 +0000
- To: public-secondscreen@w3.org
@tomoyukilabs that's very interesting, thanks for the investigation! If I understand the specs, example (note the server seems down), and results properly, only Safari has the right behavior according to specs. All other browsers close the WebSocket too early. Now, when one looks at it from an application perspective, it seems more straightforward not to have to code the logic needed to handle a message received after calling `close`, so "too early" may be what an application wants, which matches how the Presentation API is currently phrased. I'll try to create a similar test example for WebRTC. -- GitHub Notification of comment by tidoust Please view or discuss this issue at https://github.com/w3c/presentation-api/issues/240#issuecomment-173248781 using your GitHub account
Received on Wednesday, 20 January 2016 15:59:20 UTC