Closed
Bug 1844752
Opened 1 year ago
Closed 1 year ago
nsNodeInfoManager's constructor should initialize mPrincipal to the right value immediately if possible
Categories
(Core :: DOM: Core & HTML, defect, P3)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
118 Branch
| Tracking | Status | |
|---|---|---|
| firefox118 | --- | fixed |
People
(Reporter: smaug, Assigned: smaug)
References
(Blocks 2 open bugs)
Details
(Whiteboard: [sp3])
Attachments
(1 file)
It takes quite a bit time to create the NullPrincipal and then almost immediately replace that with the correct principal.
XULPrototype handling is a bit special, so I'm planning to keep the old behavior there.
|
||
Updated•1 year ago
|
See Also: → https://mozilla-hub.atlassian.net/browse/SP3-463
|
Assignee | |
Updated•1 year ago
|
Blocks: speedometer3
|
|
Assignee | |
Updated•1 year ago
|
Severity: -- → S3
Component: DOM: HTML Parser → DOM: Core & HTML
Priority: -- → P3
|
|
Assignee | |
Comment 1•1 year ago
|
||
Looks like there are also other ways to create a document when the principal isn't available immediately, so passing principal is just an optimization.
|
|
Assignee | |
Comment 2•1 year ago
|
||
Pushed by opettay@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/34c44ef4fb3e
initialize nsNodeInfoManager::mPrincipal with the correct principal when available, r=dom-core,emilio,peterv
|
||
Comment 4•1 year ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 1 year ago
status-firefox118:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 118 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•