Closed Bug 1797712 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 36686 - [IndexedDB] Add RFH Id getter from `BucketContext`

Categories

(Core :: DOM: Core & HTML, task, P4)

task

Tracking

()

RESOLVED INVALID

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Mingyu Lei <leimy@chromium.org> wrote:

[IndexedDB] Add RFH Id getter from BucketContext

This chain of CLs aims to provide a way for the IndexedDB service to
query the state of its client without introducing addition dependencies
of browser domain concepts like RenderFrameHost or back/forward cache
to the IndexedDB service, which minimize the work for the future work
when the IndexedDB need to be taken out as a standalone service
running on a separate process.

An example usage of this checker is for IDB process to determine if
the IDB client is currently inactive and thus not supposed to receive
certain events. See https://crrev.com/c/3980739.

In summary, this CL mainly does the following changes:

  1. Update the BucketContext interface to provide a getter of the
    GlobalRoutingId, and update the caller of the binding methods from
    IndexedDBControl to construct the IndexedDBClientStateChecker
    using the GlobalRoutingId and pass the remote via the mojo call.

Change-Id: I5f1d01f371ee394c770ac878bf96dfa3c8af0ebc
Bug: 1331187
Reviewed-on: https://chromium-review.googlesource.com/3980660
WPT-Export-Revision: 81820b80d6c54388e8f9a06ef3386ee953c28943

Component: web-platform-tests → DOM: Core & HTML
Product: Testing → Core
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.