New issue
Advanced search Search tips

Issue 877429 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Aug 27
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Middle mouse click in scrollbar no longer works

Reported by rew-goog...@bitwizard.nl, Aug 24

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/68.0.3440.75 Chrome/68.0.3440.75 Safari/537.36

Steps to reproduce the problem:
1. Go to any page that doesn't fit on the scren at once. Chromium bugs list works. 
2. scroll down a bit.
3. middle click on the scrollbar on the right. 

What is the expected behavior?
I'm used to having the visible window on the document jump so that the top of the "visible part" aligns with my mouse click. For example, in a long document middle click near the top to jump to the top. 

What went wrong?
The visible window no longer moves. 

leftclick in the scrollbar area scrolls towards here (up when you're above the visible part, down when you click below). That still works (but I normally don't use it: It seems I didn't know correctly what it did before researching that I wasn't saying nonsense. I was. :-) ) 

Did this work before? Yes On ubuntu: A couple of months ago. (I was hoping it would get fixed without my reporting it). 

Chrome version: 68.0.3440.75  Channel: n/a
OS Version: Ubuntu 18.04
Flash Version: dontknow

It's annoying. I use it a lot and my brain can't adjust to it no longer working. :-)
 
Today I restarted Chromium and now I notice it works again! 
Good job fixing this regression! 
(can close an issue as the owner (reporter) of an issue? )
Labels: Needs-Triage-M68 Needs-Bisect
Cc: susan.boorgula@chromium.org
Labels: -Needs-Bisect Triaged-ET
Status: WontFix (was: Unconfirmed)
Reporter@ Thanks for the update.

As per comment #1, marking this issue as WontFix as the reporter has confirmed.

Thanks..
Susan, if for whatever reason you mis-label the bugs in a big project you're going to end up with misleading statistics. 
"won'tfix" to me means "this is too much of a corner case, yes, it's a bug, but not worth the trouble fixing it". 

This is not what's going on here. I reported that the latest version that was pulled in by apt-get upgrade simply fixed the issue. Whatever it was. 

By marking bugs like this as "fix released" you are giving the programmers a pat on the back, when at the end of the month so many bugs have been marked "fix released". 

So... To help motivate those programmers, PLEASE mark this as "fixed" or something like that.... :-)

Sign in to add a comment