Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

為了改善您的使用體驗,本網站正在進行維護,部分功能暫時無法使用。若本站的文件無法解決您的問題,想要向社群發問的話,請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問,我們的社群成員將很快會回覆您的疑問。

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Forced to scroll up after going back to previous page

  • 4 回覆
  • 1 有這個問題
  • 1 次檢視
  • 最近回覆由 Peter

more options

S/W: Firefox 77.0.1 (64-bit) on Windows 10

After I go back to the previous page, Firefox forces me to scroll up.

My post on Twitter illustrates the following behaviour:

  • Open a new browser tab with Pocket articles
  • Scroll to bottom of page, then scroll back to top of page
  • With address bar, navigate to https://torontosun.com/
  • Scroll down the page
  • Go back to the prior page
  • You must now scroll up the page past all the Pocket articles

Thank you for your assistance.

Regards, Peter

S/W: Firefox 77.0.1 (64-bit) on Windows 10 After I go back to the previous page, Firefox forces me to scroll up. My post on Twitter [https://twitter.com/PSeelert/status/1271432724566458375 illustrates the following behaviour]: * Open a new browser tab with Pocket articles * Scroll to bottom of page, then scroll back to top of page * With address bar, navigate to [https://torontosun.com/ https://torontosun.com/] * Scroll down the page * Go back to the prior page * You must now scroll up the page past all the Pocket articles Thank you for your assistance. Regards, Peter

所有回覆 (4)

more options

I get around this by;
When I find a link I want to check out, I open it in a new tab/window.
Then when I am done, I close it and am back where I started.

more options

Ugh, why Firefox, why?

Somehow when you go back, the memory of the vertical scroll position in the new tab page is getting overwritten by the position on the site you visited next.

There was a problem in Firefox 76 where, when you opened a local page from disk, such as a bookmark export file, using the file:// protocol, and then scroll down and used a link to navigate to a different page that used the http:// or https:// protocol, when you went back, the scroll position was lost and the page reloaded at the top. The change that caused this was rolled back for Firefox 77.

The new tab page is an about: page, not a file:// protocol page, but the rollback may have left something in place that causes this. To tease out exactly what happened, it would be helpful for someone to:

(A) Search for any recently filed scroll position bugs on https://bugzilla.mozilla.org/ , and if one is found, probably no further action is needed unless they need another test case

(B) If there's no bug, run a mozregression to see which change caused it and file a new bug pointing the finger at that change

More info on mozregression: https://mozilla.github.io/mozregression/

more options

FredMcD said

I get around this by;
When I find a link I want to check out, I open it in a new tab/window.
Then when I am done, I close it and am back where I started.

Thank you for your suggestion. I do that, too, on sites I know behave badly, e.g. procom.ca. In the example demonstrated, there is no link to checkout. Forward navigation is executed from the address bar.

more options

jscher2000 said

Ugh, why Firefox, why? Somehow when you go back, the memory of the vertical scroll position in the new tab page is getting overwritten by the position on the site you visited next. There was a problem in Firefox 76 where, when you opened a local page from disk, such as a bookmark export file, using the file:// protocol, and then scroll down and used a link to navigate to a different page that used the http:// or https:// protocol, when you went back, the scroll position was lost and the page reloaded at the top. The change that caused this was rolled back for Firefox 77. The new tab page is an about: page, not a file:// protocol page, but the rollback may have left something in place that causes this. To tease out exactly what happened, it would be helpful for someone to: (A) Search for any recently filed scroll position bugs on https://bugzilla.mozilla.org/ , and if one is found, probably no further action is needed unless they need another test case (B) If there's no bug, run a mozregression to see which change caused it and file a new bug pointing the finger at that change More info on mozregression: https://mozilla.github.io/mozregression/

Thank you for your insights. There were similar reports raised circa Firefox 65/66 surrounding the "scroll anchoring" bug. I toggled layout.css.scroll-anchoring.enabled, but that didn't change the behaviour I noted.