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 746961 - new scroll bar "hides" after click+drag+release while mouse is still over it
new scroll bar "hides" after click+drag+release while mouse is still over it
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: .General
3.16.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2015-03-29 07:28 UTC by Branko Grubic (bitlord)
Modified: 2015-03-31 14:07 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
screencast (373.38 KB, video/webm)
2015-03-29 12:18 UTC, Christoph Reiter (lazka)
  Details
scrolledwindow: Check the event widget on captured motion events (2.27 KB, patch)
2015-03-31 11:18 UTC, Carlos Garnacho
accepted-commit_now Details | Review
scrolledwindow: Remove needless "dragging" field from Indicator struct (2.85 KB, patch)
2015-03-31 11:18 UTC, Carlos Garnacho
accepted-commit_now Details | Review

Description Branko Grubic (bitlord) 2015-03-29 07:28:25 UTC
I'm not sure how to describe this better, sorry for poor summary.
I'm using gtk3-3.16.0-1.fc22.x86_64 and when you go to some window/widget (evolution message list, nautilus, ...) which have scrollable content and for example go to vertical scroll bar it "unhides"/expands, you click and drag it up/down, then release mouse and leave it over scroll bar and scroll bar "hides" again, but I think it shouldn't do that, it should stay visible while mouse cursor is over the same area which made it "unhide"/expand. For example sometimes I use this method to search something inside scrollable widget, so I click+drag+release, and do that again (few times in a row) (searching for content, and adjusting it to be visible on screen)
Comment 1 Christoph Reiter (lazka) 2015-03-29 12:18:48 UTC
Created attachment 300535 [details]
screencast
Comment 2 Carlos Garnacho 2015-03-31 11:18:17 UTC
Created attachment 300657 [details] [review]
scrolledwindow: Check the event widget on captured motion events

This path is only intended to be triggered on events directed towards the
child of the scrolledwindow, so make it explicitly so. This avoids scrollbar
"over" state flashing when dragging finishes within the slider.
Comment 3 Carlos Garnacho 2015-03-31 11:18:23 UTC
Created attachment 300658 [details] [review]
scrolledwindow: Remove needless "dragging" field from Indicator struct

The "over" state already stays set while scrollbar dragging happens, there's
no need to double track that.
Comment 4 Matthias Clasen 2015-03-31 13:58:24 UTC
Review of attachment 300657 [details] [review]:

works nicely
Comment 5 Matthias Clasen 2015-03-31 13:58:45 UTC
Review of attachment 300658 [details] [review]:

great
Comment 6 Carlos Garnacho 2015-03-31 14:07:44 UTC
Attachment 300657 [details] pushed as eb26208 - scrolledwindow: Check the event widget on captured motion events
Attachment 300658 [details] pushed as 960c229 - scrolledwindow: Remove needless "dragging" field from Indicator struct