After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 704277 - Add scrollbar setting for chosing between place on click or Pg Up - Pg Down behavior
Add scrollbar setting for chosing between place on click or Pg Up - Pg Down b...
Status: RESOLVED OBSOLETE
Product: gnome-tweak-tool
Classification: Applications
Component: general
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: GNOME Tweak Tool maintainer(s)
GNOME Tweak Tool maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2013-07-15 17:30 UTC by Andres Gomez
Modified: 2018-01-24 15:08 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Andres Gomez 2013-07-15 17:30:13 UTC
With GTK3, now the scrollbars behave so if you click in a position in the scrollbar, the scrollbar moves to that position.

The old behavior was that clicking above the bar would mean Pg Up and clicking below Pg Down.

The old behavior can be selected adding the following option in "/etc/gtk-3.0/settings.ini" (system wide) or "~/.config/gtk-3.0/settings.ini" (user wide).

$ cat ~/.config/gtk-3.0/settings.ini
[Settings]
gtk-primary-button-warps-slider = 0

This new behavior is getting nuts to people like me without wheel in their mouse so it would be really nice if an option would be added for selecting the old behavior in the GNOME Control Center. Maybe the Mouse component is not the best, though.
Comment 1 Bastien Nocera 2013-07-16 09:05:04 UTC
I doubt this is something we want in the System Settings.

The full design for the scrollbars is at:
https://wiki.gnome.org/GnomeOS/Design/Whiteboards/Scrolling
and particular use cases are currently not working as well as they should be (which doesn't mean that simply reverting the setting would be the way to go anyway).

I'll reassign this to gnome-tweak-tool for the short-term work-around, the long term goal is to implement the missing features to make it usable in places with overly long scrollbars.
Comment 2 Andres Gomez 2013-07-16 09:10:12 UTC
(In reply to comment #1)
> I doubt this is something we want in the System Settings.
> 
> The full design for the scrollbars is at:
> https://wiki.gnome.org/GnomeOS/Design/Whiteboards/Scrolling
> and particular use cases are currently not working as well as they should be
> (which doesn't mean that simply reverting the setting would be the way to go
> anyway).
> 
> I'll reassign this to gnome-tweak-tool for the short-term work-around, the long
> term goal is to implement the missing features to make it usable in places with
> overly long scrollbars.

Nice! Thanks for the info an comments Bastien.
Comment 3 Kamil Páral 2013-07-16 13:10:59 UTC
Andrés, you can use right mouse click on the scroll bar to paginate.
Comment 4 John Stowers 2013-09-10 08:18:06 UTC
What do you think of the new scrollbar behaviour in 3.10?
Comment 5 Glenn Holmer 2013-11-05 02:52:44 UTC
It's counter-intuitive and user-hostile. It should be reverted.
Comment 6 Andrew Smith 2013-12-25 21:56:09 UTC
I've opened bug 721047 to ask that the behaviour is reverted back to normal.
Comment 7 Andrew Punnett 2016-10-26 00:21:23 UTC
(In reply to Andres Gomez from comment #0)
> The old behavior can be selected adding the following option in
> "/etc/gtk-3.0/settings.ini" (system wide) or
> "~/.config/gtk-3.0/settings.ini" (user wide).
> 
> $ cat ~/.config/gtk-3.0/settings.ini
> [Settings]
> gtk-primary-button-warps-slider = 0


Thanks for the fix. The default behaviour is very jarring and unpleasant on a system which runs a mix of GTK3 and non GTK3 software.

With the fix the scrollbar does behave erratically if the pointer is moved at all whilst holding the left mouse button.
Comment 8 Michal 'hramrach' Suchanek 2016-10-27 12:34:56 UTC
(In reply to Kamil Páral from comment #3)
> Andrés, you can use right mouse click on the scroll bar to paginate.

So if developers are so fond of new features and attaching features on right-click why cannot the new feature be attached to right click and the old feature kept intact?

Given the new feature does not seem of much use anyway having it less visible does not seem to do much harm.

(In reply to Bastien Nocera from comment #1)
> I doubt this is something we want in the System Settings.
> 
> The full design for the scrollbars is at:
> https://wiki.gnome.org/GnomeOS/Design/Whiteboards/Scrolling
> and particular use cases are currently not working as well as they should be
> (which doesn't mean that simply reverting the setting would be the way to go
> anyway).

The document dos not say anywhere I could find that page scrolling has to be broken in order to implement the new features.

> 
> I'll reassign this to gnome-tweak-tool for the short-term work-around, the
> long term goal is to implement the missing features to make it usable in
> places with overly long scrollbars.

overly long scrollbars = any place with scrollbars where they were of any use before the change
Comment 9 Michal 'hramrach' Suchanek 2016-10-27 12:45:12 UTC
btw the workaround setting does not even work.

Seems like some good intentioned soul backported the changes to gtk2 without the switch. The road to Hell is paved with good intentions, right?
Comment 10 Kamil Páral 2016-10-27 12:46:54 UTC
(In reply to Michal 'hramrach' Suchanek from comment #8)
> So if developers are so fond of new features and attaching features on
> right-click why cannot the new feature be attached to right click and the
> old feature kept intact?

It could. But my impression is that the intention was to change the default (left click).

> Given the new feature does not seem of much use anyway having it less
> visible does not seem to do much harm.

My opinion is completely different here, I consider 'jump' behavior the more useful one (that's the one I almost exclusively use, along with 'grab and drag anywhere'), and 'paginate' the less useful one (I almost never use that).

So as you can see, opinions wildly differ here. I'm personally very glad the default behavior changed, but of course I'm not disputing that tweak tool is a good place to put an option to swap those actions for people who feel differently.
Comment 11 Andrew Punnett 2016-10-31 21:05:30 UTC
(In reply to Michal 'hramrach' Suchanek from comment #9)
> btw the workaround setting does not even work.
> 
> Seems like some good intentioned soul backported the changes to gtk2 without
> the switch. The road to Hell is paved with good intentions, right?

I can confirm that the fix does not affect GTK2 applications. Does anyone know how to switch GTK2 back to the normal scrollbar behaviour?

Currently, all programs on my system except for Firefox have normal scrollbars. As you can imagine, this makes interacting with Firefox very frustrating.
Comment 12 Michal 'hramrach' Suchanek 2016-11-02 19:11:08 UTC
Themes set this option and override the system setting.

So while the fix is applicable you have to apply it per-user or fix the themes.

echo gtk-primary-button-warps-slider=0 >> ~/.gtkrc-2.0.mine
echo gtk-primary-button-warps-slider=0 >> /etc/skel/.gtkrc-2.0.mine
Comment 13 Andrew Punnett 2016-11-03 01:08:22 UTC
(In reply to Michal 'hramrach' Suchanek from comment #12)
> Themes set this option and override the system setting.
> 
> So while the fix is applicable you have to apply it per-user or fix the
> themes.
> 
> echo gtk-primary-button-warps-slider=0 >> ~/.gtkrc-2.0.mine
> echo gtk-primary-button-warps-slider=0 >> /etc/skel/.gtkrc-2.0.mine

Making the change in ~/.gtkrc-2.0 doesn't have any effect on my system (Centos 7.2). I believe this is because the setting is overridden by the gtkrc file supplied by the Adwaita theme.

I've instead "fixed" the problem by using Chromium instead of Firefox.
Comment 14 GNOME Infrastructure Team 2018-01-24 15:08:08 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-tweaks/issues/32.