Browser Console keeps scrolling after releasing mouse click

NEW
Unassigned

Status

defect
P3
normal
10 months ago
6 days ago

People

(Reporter: Fanolian+bugzilla, Unassigned)

Tracking

({regression, reproducible})

63 Branch
Dependency tree / graph

Firefox Tracking Flags

(firefox-esr60 unaffected, firefox62 unaffected, firefox63 wontfix, firefox64 wontfix, firefox65 fix-optional)

Details

Attachments

(1 attachment)

Reporter

Description

10 months ago
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:64.0) Gecko/20100101 Firefox/64.0
Build ID: 20180906100252

Steps to reproduce:

1. Open Browser Console. Create enough entries so the scrollbar is present.
2. Click and hold the scroll box/thumb. Do NOT release the mouse click.
3. Move mouse outside Browser Console window.
4. Release mouse click.
5. Move mouse back inside Browser Console.
6. Move mouse up and down.


Actual results:

Browser Console still scrolls despite having released the mouse click.

Please refer to the attached video.
P.s. my screen capture program does not record mouse clicks. Please distinguish different states by the colors of scroll box:
Dark grey: mouse clicked and held
Medium grey: mouse hovering
Light grey: mouse not clicked


Expected results:

Browser Console should not scroll after releasing mouse click.
Reporter

Comment 1

10 months ago
From Mozregression, 
Last good Nightly: 2018-07-18
First bad Nightly: 2018-07-19

regression range is:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=d94abfaa59928d8fd87f74dbde2ae82d9b7ba667&tochange=d67618d9ba00e9384114989daddbbdc86daf1ad7

Further bisection points to bug 1472599 but I think bug 1469341 may be the real cause.

Updated

10 months ago
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P3
P3, unassigned, marking fix-optional for 63
Marking fix-optional for 64. We could still take a patch for 65, and if it's verified and doesn't seem risky, could still take fixes for 64 as well.
No update over the last 2 months, updating tracking flags as we get closer to the 64 release.
Happy to take a patch in nightly; if it seems low risk enough please feel free to request uplift to 65 beta.

Comment 6

4 months ago

Hi everyone,

Can I try to solve this issue?

Thanks!

Hello Mellina,

You can definitely TRY, nto sure where you should look though.
My guess is there's an event listener on the scrollbar that sets a dragging property or something similar, and that can't catch a mouseup event outside of the window.
Brian, would you have more information on that bug?

Flags: needinfo?(bgrinstead)

(In reply to Nicolas Chevobbe from comment #7)

Hello Mellina,

You can definitely TRY, nto sure where you should look though.
My guess is there's an event listener on the scrollbar that sets a dragging property or something similar, and that can't catch a mouseup event outside of the window.
Brian, would you have more information on that bug?

I'm not sure how good of a candidate this bug is, but I'll forward to Brendan to see if he has pointers on where to start investigation.

Flags: needinfo?(bgrinstead) → needinfo?(bdahl)

(In reply to Brian Grinstead [:bgrins] from comment #8)

(In reply to Nicolas Chevobbe from comment #7)

Hello Mellina,

You can definitely TRY, nto sure where you should look though.
My guess is there's an event listener on the scrollbar that sets a dragging property or something similar, and that can't catch a mouseup event outside of the window.
Brian, would you have more information on that bug?

I'm not sure how good of a candidate this bug is, but I'll forward to Brendan to see if he has pointers on where to start investigation.

I looked briefly, but I'm really not sure what's going on here, so I don't have any good pointers without digging into it.

Flags: needinfo?(bdahl)

this issue is still happening in Firefox

changeset:   479096:9b4c8fb46d85
tag:         tip
parent:      479094:e593e11eff08
parent:      479095:adc12b4c5a9d
date:        Tue Jun 18 07:10:14 2019 +0300
summary:     Merge inbound to mozilla-central. a=merge
You need to log in before you can comment on or make changes to this bug.