Closed Bug 1533998 Opened 5 years ago Closed 5 years ago

[wpt-sync] Sync PR 15691 - [IndexedDB] Fixed DisjointRangeLockManager usage in IndexedDB

Categories

(Core :: Storage: IndexedDB, enhancement, P4)

enhancement

Tracking

()

RESOLVED FIXED
mozilla68
Tracking Status
firefox68 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 15691 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/15691
Details from upstream follow.

Daniel Murphy <dmurph@chromium.org> wrote:

[IndexedDB] Fixed DisjointRangeLockManager usage in IndexedDB

IndexedDBFactoryImpl isn't scoped per origin and so can be used by
multiple origins. The original code assumed that it was scoped per
origin, so when in actuality it was used by multiple origins, when a
single origin requested a lock this could interrupt other origins in
certain cases.

R=cmp@chromium.org
Bug: 934790
Change-Id: I10f3e7c1b43ad7310d8824648575d940568b534d
Reviewed-on: https://chromium-review.googlesource.com/1487369
WPT-Export-Revision: 036f9889c5aa83d863e3b5365ed33552b23da81a

Component: web-platform-tests → DOM: IndexedDB
Product: Testing → Core
Failed to get results from try push
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/fa3ba90635f4
[wpt PR 15691] - [IndexedDB] Fixed DisjointRangeLockManager usage in IndexedDB, a=testonly
https://hg.mozilla.org/integration/mozilla-inbound/rev/257ab48a9695
[wpt PR 15691] - Update wpt metadata, a=testonly
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/7f66506e9f7f
[wpt PR 15691] - [IndexedDB] Fixed DisjointRangeLockManager usage in IndexedDB, a=testonly
https://hg.mozilla.org/integration/mozilla-inbound/rev/b47b783658de
[wpt PR 15691] - Update wpt metadata, a=testonly
You need to log in before you can comment on or make changes to this bug.