Open Bug 1940025 Opened 25 days ago Updated 4 days ago

Navigating to URL with anchor scrolls to incorrect location in nodejs.org (with content-visibility: auto)

Categories

(Core :: Layout, defect)

Product:
Core
Component:
Layout
Version:
Firefox 133
Type:
defect

Tracking

()

Tracking Flags:
Tracking Status
firefox-esr115 --- wontfix
firefox-esr128 --- affected
firefox134 --- wontfix
firefox135 --- fix-optional
firefox136 --- affected

People

(Reporter: ddascalescu, Unassigned, NeedInfo)

References

(Blocks 1 open bug, Regression)

Details

(Keywords: regression)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:133.0) Gecko/20100101 Firefox/133.0

Steps to reproduce:

  1. Click this Node.js documentation link: https://nodejs.org/dist/v21.0.0/docs/api/globals.html#fetch

Actual results:

The page is scrolled to "Class: ReadableStreamBYOBReader"

Expected results:

Firefox should have scrolled to the "fetch" header. It does do this after pressing Enter in the URL bar.

Chromium-based browsers scroll correctly on the first navigation.

Related 24-yo bugs: #45338, #55529, #614909 (only 14yo :)

The Bugbug bot thinks this bug should belong to the 'Core::Networking' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Networking
Product: Firefox → Core

I can reproduce the issue on Nightly135.0a1 Windows11.

Steps to reproduce:

  1. Copy link https://nodejs.org/dist/v21.0.0/docs/api/globals.html#fetch to clipboard
  2. Right click on urlbar then choose Past and Go
  3. Click on link Node.js at the top-left corner of the page
  4. Again, right click on urlbar then choose Past and Go

Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=0ebda393786b0626290fd39412c47a8ba21e2171&tochange=d27fd70e433589624149fb52aa29dc2b5e5bbecf

Tentatively, set bug 1837734 as Regressed by.

Status: UNCONFIRMED → NEW
Component: Networking → Layout
Ever confirmed: true
Keywords: regression
Regressed by: 1837734

:emilio, since you are the author of the regressor, bug 1837734, could you take a look? Also, could you set the severity field?

For more information, please visit BugBot documentation.

Flags: needinfo?(emilio)

More likely to be due to bug 1838045.

This page is a bit weird because it uses content-visibility: auto, which causes the layout to shift as you scroll.

Regressed by: 1838045
No longer regressed by: 1837734
Blocks: css-content-visibility
Summary: Navigating to URL with anchor scrolls to incorrect location → Navigating to URL with anchor scrolls to incorrect location in nodejs.org (with content-visibility: auto)
See Also: → 1880928

Set release status flags based on info from the regressing bug 1838045

status-firefox134: --- → affected
status-firefox135: --- → affected
status-firefox136: --- → affected
status-firefox-esr128: --- → affected

For some reason I get expected-results here if I Shift+Click on the link (for open-in-new-window), whereas I get actual-results if I ctrl+click (open-in-new-tab) or just directly click on the link. (Presumably that's just a bit of luck from the overhead of setting up a new Firefox window, which maybe changes the ordering of events here slightly.)

Severity: -- → S3
You need to log in before you can comment on or make changes to this bug.