- From: François Daoust via GitHub <sysbot+gh@w3.org>
- Date: Fri, 05 Feb 2016 14:47:05 +0000
- To: public-secondscreen@w3.org
tidoust has just created a new issue for https://github.com/w3c/presentation-api: == Should `reconnect` fire a `connectionavailable` event when it returns an existing presentation connection? == Right now, the `reconnect` procedure always fires a `connectionavailable` event, even when it returns a `PresentationConnection` object created by the current browsing context. Without having given it much thoughts, I would rather assume that a given `PresentationConnection` instance would only trigger one `connectionavailable` event. That seems to match the description of the `PresentationConnectionAvailableEvent` interface, which suggests that the event only fires "when a connection associated with the [PresentationRequest] object is **created**". Fake code example: ```js var connection = null; var presId = null; var request = new PresentationRequest(url); request.onconnectionavailable = function (evt) { connection = evt.connection; }); [...] // Call to start will trigger a "connectionavailable" event request.start(); [...] // Call to reconnect will return the same connection instance, // should it really trigger another "connectionavailable" event? request.reconnect(presId); ``` Please view or discuss this issue at https://github.com/w3c/presentation-api/issues/259 using your GitHub account
Received on Friday, 5 February 2016 14:47:07 UTC