Repository navigation
define the behavior for consecutive |getAvailability| #335
Description
Three unclear behavior found while implementing the |getAvailability| algorithm:
- In step 6, the same availability object is returned if an existed
(A, presentationUrls)tuple is found. However, we can only return the same object if the requester is in the same DOM window. - in step 9, we should run the device monitoring algorithm in parallel so that we can resolve the promise as early as possible.
- For consecutive |getAvailability| on the same
PresentationRequestobject, we should guarantee the resolve order in the algorithm. For example,
request.getAvailability().then(function() {console.log(1)});
request.getAvailability().then(function() {console.log(2)});
should always print "12" in console for all browsers.
Activity
tidoust commentedon Sep 26, 2016
See discussion at TPAC
PROPOSED RESOLUTION: For #335, check algorithms around availability objects and make sure they all refer to "script object" or "internal object". For bullet 2, add "in parallel" in step 9. For bullet 3, make sure
getAvailabilityreturns the samePromiseobject.markafoltz commentedon Sep 30, 2016
Section 6.4 will need a bit of cleanup to make it consistent with reasonable behavior. Here is what I am thinking.
getAvailability()withSameObject.Can start after the PR for Issue #342 lands (which tweaks some text in this same section).