Autoscroll no longer works on about:* pages (except about:newtab)
Categories
(Core :: DOM: UI Events & Focus Handling, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr78 | --- | unaffected |
firefox86 | --- | unaffected |
firefox87 | --- | unaffected |
firefox88 | --- | unaffected |
firefox89 | + | verified |
People
(Reporter: cmuresan, Assigned: masayuki)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
[Affected versions]:
- Firefox Nightly 89.0a1, Build ID 20210324160546
[Affected Platforms]:
- Windows 10
- macOS 10.15
- Ubuntu 20.04 (with
general.autoScroll
set totrue
)
[Prerequisites]:
- Have a new Firefox profile.
[Steps to reproduce]:
- Open the browser with the profile from prerequisites.
- Navigate to the about:support page.
- Initiate an autoscroll event using the middle mouse button (scroll) and move the mouse down.
- Observe the behavior.
[Expected results]:
- The page is scrolled downwards.
[Actual results]:
- Autoscroll is not triggered in the page.
[Regression Window]:
2:52.86 INFO: Last good revision: 630002d187a1f7c9a7c61dcf4b8fc110698b665b
2:52.86 INFO: First bad revision: 8fcec4a428e2b9b6595c69511aae4429881d0c52
2:52.86 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=630002d187a1f7c9a7c61dcf4b8fc110698b665b&tochange=8fcec4a428e2b9b6595c69511aae4429881d0c52
From the pushlog it looks like bug 1686662 has caused this.
@masayuki, could you please take a look at this?
[Notes]:
- The issue is also reproducible on the about:preferences, about:addons, about:telemetry pages.
Reporter | ||
Updated•3 years ago
|
Reporter | ||
Updated•3 years ago
|
Assignee | ||
Comment 1•3 years ago
|
||
Sure.
Updated•3 years ago
|
Assignee | ||
Comment 2•3 years ago
|
||
When active tab loads about:*
which is in the chrome process, focused element
is null. Therefore, the check whether the browser element of AutoScrollParent
is active tab or not does not work as expected. And the new check was added
for web apps which don't call preventDefault()
properly after opening new
tab of a middle mouse button click. So, our chrome document must not require
this hack. So, we keep the old behavior when the browser is not a remote one.
Updated•3 years ago
|
Updated•3 years ago
|
Pushed by masayuki@d-toybox.com: https://hg.mozilla.org/integration/autoland/rev/74a82f46f9ae Make `AutoScrollParent` always consider starting autoscroll when it's requested in non-remote browser element r=Gijs
Comment 4•3 years ago
|
||
bugherder |
Reporter | ||
Comment 5•3 years ago
|
||
I have verified that the issue is no longer reproducible on as many about:* pages that had scrollbars (I used about:about) on the latest Nightly 89.0a1 (Build ID 20210331215444) using Windows 10, macOS 11.2.3, and Linux MX 4.19.
Updated•3 years ago
|
Description
•