Closed
Bug 1670973
Opened 4 years ago
Closed 3 years ago
Test how session history loads triggering http redirects affect to other entries in session history
Categories
(Core :: DOM: Navigation, task, P3)
Core
DOM: Navigation
Tracking
()
People
(Reporter: smaug, Assigned: smaug)
References
(Blocks 1 open bug)
Details
(Whiteboard: fission-hard-blocker)
Attachments
(1 file)
Bug 1668083 fixes some part of redirect handling, but we don't have tests for all the cases.
Should a redirect from a load triggered from session history be treated as a new load or as a replacement from session history point of view?
Updated•4 years ago
|
Severity: -- → N/A
Fission Milestone: --- → M6c
Priority: -- → P3
Comment 1•4 years ago
|
||
Haven't seen any redirect breakage recently so this investigation can be done in M7.
Fission Milestone: M6c → M7
Updated•3 years ago
|
Fission Milestone: M8 → MVP
Comment 3•3 years ago
|
||
Olli is still waiting for a spec test from Google.
Comment 4•3 years ago
|
||
This bug is a hard blocker for Fission MVP.
status-firefox92:
--- → affected
Whiteboard: fission-hard-blocker
Assignee | ||
Comment 5•3 years ago
|
||
The old implementation and SHIP seem to have the same behavior.
Pushed by opettay@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/20cdfb2cb9d9
add a test to check how http redirects affect to the session history, r=peterv
Comment 7•3 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox93:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 93 Branch
Updated•3 years ago
|
Flags: in-testsuite+
You need to log in
before you can comment on or make changes to this bug.
Description
•