Closed Bug 2021684 Opened 6 months ago Closed 5 months ago

[Regression] Page jumps to top when scrolling on apply.careers.microsoft.com (Regressed by Bug 2016967)

Categories

(Core :: Panning and Zooming, defect, P2)

Firefox 150
defect

Tracking

()

RESOLVED FIXED
Tracking Status
firefox-esr140 --- unaffected
firefox148 --- unaffected
firefox149 --- unaffected
firefox150 + fixed

People

(Reporter: nish, Assigned: jjaschke)

References

(Regression, )

Details

(Keywords: regression)

Attachments

(2 files)

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

Steps to reproduce:

steps:

  1. click on any job, for example: https://apply.careers.microsoft.com/careers/apply?pid=1970393556753425
  2. sign in
  3. scroll down

Actual results:

scroll repeatedly jumps to top

Expected results:

should have let user scroll

i used mozregression and found this bug was responsible

Bug 2016967 - Fix find-in-page not scrolling to sticky table cells by using natural frame position in ScrollFrameIntoView. r=emilio,layout-reviewers

Differential Revision: https://phabricator.services.mozilla.com/D285547

2026-03-07T15:13:44.601000: DEBUG : Did not find a branch, checking all integration branches
2026-03-07T15:13:44.601000: INFO : The bisection is done.
2026-03-07T15:13:44.602000: INFO : Stopped

Keywords: regression
Regressed by: 2016967

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

Component: Untriaged → Panning and Zooming
Product: Firefox → Core

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

For more information, please visit BugBot documentation.

Flags: needinfo?(jjaschke)

[Tracking Requested - why for this release]: Can repro this regression and seems easy to trigger.

What seems to be going on is that we're scrolling to the normal position even though the sticky item is visible already.

Severity: -- → S2
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P2

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

Thanks for the report, and thanks Emilio for the reduced test case.

I think that the behavior I introduced in bug 2016967 should only apply for find-in-page/text-fragment scroll, and not in general. I believe that the WPT I added in that bug is also not correct.

Flags: needinfo?(jjaschke)
Assignee: nobody → jjaschke
Status: NEW → ASSIGNED

I also see this bug when trying to scroll this page: https://moglang.org/

Jan wdyt of backing out or putting your original fix behind a pref for now? I think it's on the right track but clearly needs some more work?

Flags: needinfo?(jjaschke)
See Also: → 2019912

Yeah, I'll request backout, I'll likely not be able to work on this for the next days.

Flags: needinfo?(jjaschke)

Setting Fx150 to fixed since Bug 2016967 was backed out from firefox-main

(In reply to Donal Meehan [:dmeehan] from comment #12)

Setting Fx150 to fixed since Bug 2016967 was backed out from firefox-main

IIUC, we can close this as FIXED for the same reason. I'll add a note on Bug 2016967 to be sure we avoid regressing this (or put the changes behind a pref, etc) when re-landing.

Closing as FIXED-by-backout.

Status: ASSIGNED → RESOLVED
Closed: 5 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: