Andreas Butler 82dd133f9e Bug 1523562 [wpt PR 14420] - [WebLocks]: Modifying weblocks algos to be O(1), a=testonly ... Automatic update from web-platform-tests [WebLocks]: Modifying weblocks algos to be O(1) The behaviour of the request/release operations of web locks are modified to be O(1) instead of their currently O(n) worst case runtime. Additionally the query-order wpt is modified to reflect the new spec requirement that the state returned by navigator.locks.query need only respect ordering for requested locks per resource. Bug: 913014 Change-Id: I819f8c27c995cb698a7c8b2c75ee80d32c744f07 Spec: https://wicg.github.io/web-locks/#algorithms Reviewed-on: https://chromium-review.googlesource.com/c/1367910 Commit-Queue: Andreas Butler <andreasbutler@google.com> Reviewed-by: Victor Costan <pwnall@chromium.org> Reviewed-by: Joshua Bell <jsbell@chromium.org> Reviewed-by: Daniel Murphy <dmurph@chromium.org> Cr-Commit-Position: refs/heads/master@{#621833} -- wpt-commits: 27085bc4fef9a55a5f5dd530c6e8ff798ff8c6c4 wpt-pr: 14420		2019-02-07 21:50:54 +00:00
..
helpers.js	Bug 1523562 [wpt PR 14420] - [WebLocks]: Modifying weblocks algos to be O(1), a=testonly	2019-02-07 21:50:54 +00:00
iframe.html	Bug 1523562 [wpt PR 14420] - [WebLocks]: Modifying weblocks algos to be O(1), a=testonly	2019-02-07 21:50:54 +00:00
service-worker.js
sw-controlled-iframe.html
worker.js