Base URI of initial about:blank is incorrectly about:blank
Categories
(Core :: DOM: Navigation, defect, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr140 | --- | unaffected |
| firefox145 | --- | unaffected |
| firefox146 | --- | unaffected |
| firefox147 | --- | disabled |
| firefox148 | --- | fixed |
People
(Reporter: vhilla, Assigned: vhilla)
References
(Regression)
Details
(Keywords: regression)
Attachments
(2 files)
STR:
- Go to some page like
https://example.com, ensure you have user activation and execute the following code console.log(window.open("about:blank").document.baseURI)
Expectation: https://example.com
Actual: about:blank
Cause: I expect nsWindowWatcher::OpenWindowInternal has to set openWindowInfo->mBaseUriToInheritForAboutBlank. But I'm unsure based on what conditions that should happen.
| Assignee | ||
Updated•2 months ago
|
Comment 1•2 months ago
|
||
Set release status flags based on info from the regressing bug 543435
| Assignee | ||
Updated•2 months ago
|
| Assignee | ||
Comment 3•2 months ago
|
||
| Assignee | ||
Comment 4•2 months ago
|
||
For web compat, it suffices to have the right base URI once the initial
document is being loaded. This means we can match what would happen in
Document::Reset, instead of propagating the base URI via nsOpenWindowInfo.
Comment 5•2 months ago
|
||
Bug 543435 was reverted from Fx147. Updating the flags accordingly.
Updated•2 months ago
|
| Assignee | ||
Comment 6•2 months ago
|
||
| Assignee | ||
Comment 7•1 month ago
|
||
| Assignee | ||
Comment 8•1 month ago
|
||
Comment 11•1 month ago
|
||
| Assignee | ||
Comment 13•1 month ago
•
|
||
https://html.spec.whatwg.org/#following-hyperlinks-2 step 7 chooses a navigable with "subject's node navigable" as current navigable / creator. So for link clicks, OpenWindowInternal needs to use parentDoc.
https://html.spec.whatwg.org/#window-open-steps step 2, 13 on the other hand uses the entry global's navigable as creator. So for window.open, we want to use the entry global as my patch does.
Maybe we can try to use the entry global and otherwise fall back to parentDoc. Or we accept that window.open incorrectly uses the parent instead of entry global.
| Assignee | ||
Comment 14•1 month ago
|
||
(In reply to Vincent Hilla [:vhilla] from comment #13)
Maybe we can try to use the entry global and otherwise fall back to
parentDoc.
Comment 15•1 month ago
|
||
Comment 17•1 month ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/00767bd39f44
https://hg.mozilla.org/mozilla-central/rev/d4561e2a7b33
Description
•