Closed
Bug 1908002
Opened 3 months ago
Closed 3 months ago
Expose LockManager in the parent process so that the browser UI can use it
Categories
(Core :: DOM: Core & HTML, enhancement)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
130 Branch
| Tracking | Status | |
|---|---|---|
| firefox130 | --- | fixed |
People
(Reporter: mconley, Assigned: mconley)
References
Details
Attachments
(1 file)
We'd like to use the Web Locks API on the front-end to do some sequencing of various asynchronous things (to avoid interleaving them). The Web Locks API seems like what we want, but is currently restricted to content principals.
I'm wondering if we'd be willing to let the parent process system principal construct a LockManager, and to allow it to be exposed to modules via Cu.importGlobalProperties?
That's what this bug's about.
|
Assignee | |
Comment 1•3 months ago
|
||
|
|
Assignee | |
Updated•3 months ago
|
Summary: Expose LockManager via the BackstagePass global to privileged module execution scopes in the parent process → Expose LockManager in the parent process so that the browser UI can use it
|
||
Updated•3 months ago
|
Attachment #9412864 -
Attachment description: Bug 1908002 - Allow LockManager to be constructed in the parent process with the system principal and loaded in modules. r?saschanaz! → Bug 1908002 - Allow LockManager to be constructed in the parent process with the system principal and loaded in modules. r?saschanaz!,smaug!
Pushed by mconley@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/45cd406f10a1
Allow LockManager to be constructed in the parent process with the system principal and loaded in modules. r=saschanaz,smaug
|
||
Comment 3•3 months ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 3 months ago
status-firefox130:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 130 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•