W3C home > Mailing lists > Public > public-secondscreen@w3.org > August 2015

[presentation-api] Let getAvailability() resolve its promise as soon as availability has been tested

From: Philip Jägenstedt via GitHub <sysbot+gh@w3.org>
Date: Wed, 19 Aug 2015 12:45:26 +0000
To: public-secondscreen@w3.org
Message-ID: <issues.opened-101884454-1439988324-sysbot+gh@w3.org>
foolip has just created a new issue for 
https://github.com/w3c/presentation-api:

== Let getAvailability() resolve its promise as soon as availability 
has been tested ==
http://w3c.github.io/presentation-api/#dom-presentationrequest-getavailability

Reliable sources (@avayvod) tell me that the implementation in 
Chromium "will resolve the promise with availability false and then 
update the value with true as soon as the first device is found" which
 isn't what the spec says.

The exact details are editorial, but I would propose to resolve the 
promise within the definition of getAvailability() and to let the 
monitoring steps only fire events in case of changes.

See https://github.com/w3c/presentation-api/issues/161
Received on Wednesday, 19 August 2015 12:45:27 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 19 August 2015 12:45:28 UTC