Closed Bug 1670256 Opened 5 years ago Closed 5 years ago

[Fission] After a redirection, scroll position is not retained after going back a page

Categories

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

defect

Tracking

()

RESOLVED DUPLICATE of bug 1668083
Fission Milestone M6c
Tracking Status
firefox81 --- unaffected
firefox82 --- unaffected
firefox83 --- disabled

People

(Reporter: Fanolian+BMO, Unassigned)

References

(Blocks 1 open bug, )

Details

(Keywords: nightly-community, regression, reproducible)

Attachments

(1 file)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:83.0) Gecko/20100101 Firefox/83.0
Build ID: 20201009041754

Steps to reproduce

  1. Enable fission.
  2. Go to https://www.hkepc.com/forum , which has a 301 Moved Permanently to https://www.hkepc.com/forum/ .
  3. Scroll down.
  4. Press a link that opens in the same tab. (Most non-ads will do.)
  5. Go back 1 page.

Actual result

Scroll position is not retained. The page goes back to the top. (see attached video)

Expected result

I do not lose the scroll position.

Notes

If I visit https://www.hkepc.com/forum/ directly and repeat step 3 to 5, the bug is not exhibited.
Reloading the page, even when URL bar shows https://www.hkepc.com/forum/, still exhibit the bug.

Workaround

Disable Fission.

For Mozregression:
Last good Nightly: 2020-10-02
First bad Nightly: 2020-10-03
pushlog: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=c25899d7b631470b983650ee254177381a62eaad&tochange=33139800aca52aac192973fe24c9b74df7c87e00

Bisecting autoland builds:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=ee7eeea3fb66321fabf86ffd3a1caf4fa3511e43&tochange=1aa67f749387d4d6d26f7d69511434ac71112110

This is regressed by bug 1668357.

Setting the tracking status for 83 to disabled as Fission is Nightly only.

Has Regression Range: --- → yes
Has STR: --- → yes
Regressed by: 1668357
No longer regressed by: 1668357
Severity: -- → S3
Fission Milestone: --- → M6c
Priority: -- → P3

Note, there were changes to redirect handling + session history last night, but I don't think that would have helped here.
But please test using the latest nightly.

This is fixed by bug 1668083. Thanks!

Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
Resolution: WORKSFORME → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: