[Regression] Page jumps to top when scrolling on apply.careers.microsoft.com (Regressed by Bug 2016967)
Categories
(Core :: Panning and Zooming, defect, P2)
Tracking
()
| 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:
- click on any job, for example: https://apply.careers.microsoft.com/careers/apply?pid=1970393556753425
- sign in
- scroll down
Actual results:
scroll repeatedly jumps to top
Expected results:
should have let user scroll
| Reporter | ||
Comment 1•6 months ago
|
||
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
| Reporter | ||
Updated•6 months ago
|
Comment 2•6 months ago
|
||
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.
Comment 3•6 months ago
|
||
: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.
Comment 4•6 months ago
|
||
[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.
Comment 5•6 months ago
|
||
Updated•6 months ago
|
Comment 6•6 months ago
|
||
Set release status flags based on info from the regressing bug 2016967
| Assignee | ||
Comment 7•6 months ago
|
||
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.
| Assignee | ||
Comment 8•6 months ago
|
||
Updated•6 months ago
|
Updated•6 months ago
|
Comment 9•6 months ago
|
||
I also see this bug when trying to scroll this page: https://moglang.org/
Comment 10•6 months ago
|
||
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?
| Assignee | ||
Comment 11•6 months ago
|
||
Yeah, I'll request backout, I'll likely not be able to work on this for the next days.
Comment 12•6 months ago
|
||
Setting Fx150 to fixed since Bug 2016967 was backed out from firefox-main
Comment 13•5 months ago
|
||
(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.
Comment 14•5 months ago
|
||
Closing as FIXED-by-backout.
Description
•