- From: François Daoust via GitHub <sysbot+gh@w3.org>
- Date: Thu, 01 Dec 2016 16:32:47 +0000
- To: public-secondscreen@w3.org
tidoust has just created a new issue for https://github.com/w3c/presentation-api: == Step 11 of getAvailability should not run "in parallel" == I failed to notice that when I reviewed the update, but I think "in parallel" is wrong in step 11 of the `getAvailability` algorithm which instructs the user agent to "Run the algorithm to monitor the list of available presentation displays in parallel". In practice, if the algorithm is run in parallel, that means the first time an app calls `getAvailability`, it will always end up with a `PresentationAvailability` object whose `value` is `false` (set by step 9.1 since the list of available presentation displays is empty to start with). Is that the intent? I would rather expect the `value` to convey the outcome of running the monitoring algorithm. Please view or discuss this issue at https://github.com/w3c/presentation-api/issues/381 using your GitHub account
Received on Thursday, 1 December 2016 16:32:54 UTC