Over scrolling when mouse down on scrollbar if smooth scroll is enabled

NEW
Assigned to

Status

()

Core
Layout
P3
normal
9 months ago
3 months ago

People

(Reporter: Alice0775 White, Assigned: kip)

Tracking

({regression, ux-consistency})

34 Branch
All
Windows 10
regression, ux-consistency
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox50 wontfix, firefox51 wontfix, firefox52 fix-optional, firefox53 wontfix, firefox54 fix-optional)

Details

(Whiteboard: [DUPEME],[parity-Chrome][parity-Edge])

(Reporter)

Description

9 months ago
Build Identifier:
https://hg.mozilla.org/mozilla-central/rev/5ce3882eec21be3a70e4afc050959ca2f76bfa76
Mozilla/5.0 (Windows NT 10.0; WOW64; rv:53.0) Gecko/20100101 Firefox/53.0 ID:20170115030210

The problem is noticeable on long page. 
Over scrolling when mouse down on scrollbar. It is not intuitive behavior.
Disabled smooth scroll fix the problem.

Reproducible: always

Steps To Reproduce:
1. Open long page (e.g., https://developer.mozilla.org/en-US/docs/Web/Events )
2. Mouse down and keep on the empty area of vertical scrollbar and do not move mouse pointer
3. wait to stop scroll
   --- observe page scroll position, and thumb position
4. Mouse up and click (also do not move mouse pointer)
   --- observe page scroll position, and thumb position

Actual Results:
Page is over scrolling.
The thumb is overshoot beyond position the mouse pointer.
After Step4, scroll position of page is going back.

Expected Results:
Page should not be over scrolling. (Edge and Chrome does).
After Step4, scroll position of page should not be going back.

Regression window:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=ec4622e6e1fa&tochange=4ef03db1385b

Regressed by: Bug 957445

Comment 1

9 months ago
Maybe the same underlying issue as in bug 1328053?
Flags: needinfo?(kgilbert)
status-firefox50: --- → affected
status-firefox51: --- → affected
status-firefox52: --- → affected
(Assignee)

Comment 2

9 months ago
Indeed, this may be the same root cause.  I am adding a patch to Bug 1328053, which may fix this as well.  Once Bug 1328053 lands, please re-test to see if it is fully fixed.
Depends on: 1328053
Flags: needinfo?(kgilbert)
(Assignee)

Comment 3

9 months ago
I have pushed a series of try builds out for the proposed fix to Bug 1328053.  Hopefully we can use these builds to verify that it fixes this bug also.
(Assignee)

Comment 4

9 months ago
I've reproduced this (Windows 10, FF Nightly).  It appears the fix to Bug 1328053 does not correct it.
(Reporter)

Updated

9 months ago
status-firefox50: affected → wontfix
status-firefox51: affected → wontfix
status-firefox54: --- → affected
Still reproducible, but I think this is edge-case enough that I'm calling it fix-optional for 52. That said, we still have time to take a low-risk fix for 52 if you have more time to look into this, Kip :)
status-firefox52: affected → fix-optional
Flags: needinfo?(kgilbert)
(Assignee)

Comment 6

8 months ago
(In reply to Ryan VanderMeulen [:RyanVM] from comment #5)
> Still reproducible, but I think this is edge-case enough that I'm calling it
> fix-optional for 52. That said, we still have time to take a low-risk fix
> for 52 if you have more time to look into this, Kip :)

I won't likely have time to investigate this one before the trains run, but would be glad to take a look for the following release.

I'll take the bug for now, but please feel free to steal this from me if anyone wants to get it in for 52.
Assignee: nobody → kgilbert
Flags: needinfo?(kgilbert)
Too late for a fix for 53, fix-optional for 54, minor carryover regression.
status-firefox53: affected → wontfix
status-firefox54: affected → fix-optional

Updated

5 months ago
Duplicate of this bug: 1369847

Updated

3 months ago
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.