Closed Bug 1670973 Opened 2 years ago Closed 10 months ago

Test how session history loads triggering http redirects affect to other entries in session history

Categories

(Core :: DOM: Navigation, task, P3)

task

Tracking

()

RESOLVED FIXED
93 Branch
Fission Milestone MVP
Tracking Status
firefox92 --- wontfix
firefox93 --- fixed

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?

Severity: -- → N/A
Fission Milestone: --- → M6c
Priority: -- → P3

Haven't seen any redirect breakage recently so this investigation can be done in M7.

Fission Milestone: M6c → M7

not a beta blocker

Fission Milestone: M7 → M8
Fission Milestone: M8 → MVP

Olli is still waiting for a spec test from Google.

This bug is a hard blocker for Fission MVP.

Whiteboard: fission-hard-blocker

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
Status: NEW → RESOLVED
Closed: 10 months ago
Resolution: --- → FIXED
Target Milestone: --- → 93 Branch
You need to log in before you can comment on or make changes to this bug.