Closed
Bug 1944718
Opened 1 year ago
Closed 1 year ago
NTP body content shifts when scrolling up with browser.newtabpage.activity-stream.showSearch = false
Categories
(Firefox :: New Tab Page, defect)
Firefox
New Tab Page
Tracking
()
VERIFIED
FIXED
137 Branch
People
(Reporter: yoasif, Assigned: thecount)
References
(Blocks 1 open bug)
Details
(Keywords: nightly-community)
Attachments
(3 files, 1 obsolete file)
Steps to reproduce:
- Set
browser.newtabpage.activity-stream.showSearchto false - open new tab
- scroll down
- scroll up
What happens:
The top sites and below jump up.
Expected result:
There should be no jumpiness.
Screencast attached.
| Reporter | ||
Comment 1•1 year ago
|
||
Attachment #9462673 -
Attachment is obsolete: true
| Reporter | ||
Updated•1 year ago
|
Has STR: --- → yes
Keywords: nightly-community
| Assignee | ||
Updated•1 year ago
|
Assignee: nobody → sdowne
| Assignee | ||
Comment 2•1 year ago
|
||
Pushed by sdowne@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/29067c6838d0
Newtab fixing fixed search position if search is turned off r=home-newtab-reviewers,maxx
Comment 4•1 year ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 1 year ago
status-firefox137:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 137 Branch
Comment 7•1 year ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D236891
Updated•1 year ago
|
Attachment #9465304 -
Flags: approval-mozilla-beta?
Comment 8•1 year ago
|
||
beta Uplift Approval Request
- User impact if declined: Content shifting when search is turned off
- Code covered by automated testing: yes
- Fix verified in Nightly: no
- Needs manual QE test: yes
- Steps to reproduce for manual QE testing: Steps in bugzilla
- Risk associated with taking this patch: low
- Explanation of risk level: It's a small block of JS change
- String changes made/needed: None
- Is Android affected?: no
Flags: qe-verify+
Updated•1 year ago
|
Attachment #9465304 -
Flags: approval-mozilla-beta? → approval-mozilla-beta+
Updated•1 year ago
|
status-firefox136:
--- → fixed
Updated•1 year ago
|
QA Whiteboard: [qa-triaged]
Comment 10•11 months ago
|
||
I have reproduced this issue using Firefox 136.0a1 (2025.01.29) on Windows 11.
I can confirm this issue is fixed, I verified using Firefox 136.0.4 and Firefox 137.0.1 on Windows 11, Ubuntu 22 and on macOS 10.15.
Status: RESOLVED → VERIFIED
Flags: qe-verify+
You need to log in
before you can comment on or make changes to this bug.
Description
•