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 737843 - Scrolling broken with gtk-primary-button-warps-slider = false
Scrolling broken with gtk-primary-button-warps-slider = false
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: .General
3.13.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2014-10-03 12:49 UTC by Christoph Reiter (lazka)
Modified: 2016-01-30 17:30 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
screencast (909.71 KB, video/webm)
2014-10-31 15:33 UTC, Christoph Reiter (lazka) 		Details

Description Christoph Reiter (lazka) 2014-10-03 12:49:16 UTC 
Setting gtk-primary-button-warps-slider to false (some themes do in settings.ini) makes clicking on scales and scrollbars behave weird. Clicking jumps to the start instead of scrolling a page.

This can be seen in "gtk3-widget-factory" with the scales on page 1 and the scrolled window with colors on page 3 and the volume button on page 2.
Comment 1 Matthias Clasen 2014-10-04 02:38:35 UTC 
can't reproduce this, are you seeing it with 3.14.0 or 3.14.1 ?
Comment 2 Christoph Reiter (lazka) 2014-10-31 15:33:49 UTC 
Created attachment 289749 [details]
screencast

Yes, also with current trunk. See attached screencast.
Comment 3 haarp 2015-03-27 15:10:10 UTC 
I can confirm this bug in gtk+ 3.14, using pavucontrol's volume sliders. If the click is accompanied by even the slightest mouse movement, the slider instantly resets to 0.

3.12 did not show this behavior.
Comment 4 draymond 2015-05-03 19:29:15 UTC 
I can confirm this bug still exists in GTK+ 3.16.2.
Comment 5 Christoph Reiter (lazka) 2015-09-13 06:09:57 UTC 
I can't reproduce this anymore with 3.16.6. Can anyone confirm?
Comment 6 Matthias Clasen 2016-01-30 17:30:25 UTC 
assuming it is gone, then