Closed
Bug 1477995
Opened 7 years ago
Closed 1 year ago
Surplus scrolling when stop autoscroll with mouse wheel over the autoscroll marker
Categories
(Core :: Graphics: WebRender, defect, P5)
Tracking
()
RESOLVED
INACTIVE
Tracking | Status | |
---|---|---|
firefox-esr52 | --- | unaffected |
firefox-esr60 | --- | unaffected |
firefox61 | --- | unaffected |
firefox62 | --- | disabled |
firefox63 | --- | affected |
People
(Reporter: alice0775, Unassigned)
References
(Depends on 1 open bug)
Details
+++ This bug was initially created as a clone of Bug #1444845 +++
The problem is only happens with WebRender enabled.
Reproduce: always
Steps To Reproduce:
0. Enable WebRender
1. Open any long page such as http://archive.mozilla.org/pub/firefox/nightly/2017/12/
2. Middle click on empty area so that perform autoscroll (do not move mouse pointer)
3. Turn mouse wheel over the autoscroll marker
Actual Results:
Surplus scrolling occurs. And then the autoscroll marker disappears
Expected Results:
No such surplus scrolling. Just the autoscroll marker disappears
![]() |
Reporter | |
Updated•7 years ago
|
Component: XUL Widgets → Graphics: WebRender
Product: Toolkit → Core
Comment 1•7 years ago
|
||
I can reproduce on Windows. Given that the non-WR version of this was fixed by bug 1467867, this is likely a failure to propagate hit-test information from the UI process into the content process.
Blocks: stage-wr-trains
Priority: -- → P3
Updated•7 years ago
|
Priority: P3 → P4
Comment 2•7 years ago
|
||
Kats - How bad is this? (I assume this is still reproducible.) How likely is it that an nvidia chip user will hit this?
Flags: needinfo?(kats)
Comment 3•7 years ago
|
||
(In reply to Maire Reavy [:mreavy] Plz needinfo from comment #2)
> Kats - How bad is this?
Pretty minor interaction difference in the grand scheme of things. Doing the wheel scroll does also exit autoscroll, it just does a scroll *in addition* to that. Which is probably not a big deal; most people don't even use autoscroll and those that do likely use the middle-click to exit it. We can drop this from the MVP.
> (I assume this is still reproducible.)
Yes
> How likely
> is it that an nvidia chip user will hit this?
The codepath is hardware-independent, so it should affect all users.
Flags: needinfo?(kats)
Comment 4•6 years ago
|
||
If we fix bug 1536520 this bug will become a no-op, since mousewheel won't interrupt autoscrolling anymore.
Depends on: 1536520
Priority: P4 → P5
Updated•3 years ago
|
Severity: normal → S3
Updated•1 year ago
|
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•