history_reload_referrer.html WPT fails on Chromium and WebKit
Categories
(Core :: DOM: Navigation, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox123 | --- | unaffected |
firefox124 | --- | unaffected |
firefox125 | --- | wontfix |
firefox126 | --- | fixed |
People
(Reporter: mjurgens, Assigned: mjurgens)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
The WPT I landed yesterday in Bug 1881533 seems to fail on Chromium and WebKit. What the test is meant to test (the referrer behavior on history.pushState/replaceState and fragment navigation) seems to be the same in all browsers and is not the problem. Rather, there seems to be a problem with the referrer on location.reload()
, which I described in Bug 1883638 now. That is also why I didn't catch this before landing the test, because I only tested history.pushState
directly in Chrome and not the final WPT.
Assignee | ||
Updated•3 months ago
|
Comment 1•3 months ago
|
||
Set release status flags based on info from the regressing bug 1881533
Assignee | ||
Updated•3 months ago
|
Assignee | ||
Comment 2•3 months ago
|
||
This test was added prematurely, as it does not make sense to test until the
question arround the referrer behaviour on location.reload()
described in
Gecko Bug 1883638 is resolved.
Updated•3 months ago
|
Comment 3•3 months ago
|
||
Set release status flags based on info from the regressing bug 1881533
Comment 4•3 months ago
|
||
Setting 125 back to affected since the regressor landed there.
:mjurgens/:fredfy, does this need to land soon? The patch has been pending review for the last two weeks
Assignee | ||
Updated•3 months ago
|
Pushed by mjurgens@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/3e43145a7567 Remove WPT history_reload_referrer.html again r=freddyb
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/45251 for changes under testing/web-platform/tests
Comment 8•3 months ago
|
||
bugherder |
Upstream PR merged by moz-wptsync-bot
Comment 10•3 months ago
|
||
The patch landed in nightly and beta is affected.
:mjurgens, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- If no, please set
status-firefox125
towontfix
.
For more information, please visit BugBot documentation.
Assignee | ||
Updated•3 months ago
|
Description
•