A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://github.com/w3c/presentation-api/issues/335 below:

define the behavior for consecutive |getAvailability| · Issue #335 · w3c/presentation-api · GitHub

Three unclear behavior found while implementing the |getAvailability| algorithm:

  1. 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.
  2. in step 9, we should run the device monitoring algorithm in parallel so that we can resolve the promise as early as possible.
  3. For consecutive |getAvailability| on the same PresentationRequest object, 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.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4