GNOME Bugzilla – Bug 740011
overscroll overlay is opaque in unfocused mode sidebars
Last modified: 2014-11-13 19:28:35 UTC
Created attachment 290512 [details] screenshot Open Nautilus or gtk3-demo, then focus another window, and try scrolling the sidebar so that the blue overscroll overlay appears. Notice that the overlay is completely opaque. (This only happens with the sidebar, not main view.) gtk 3.15.1-197-ge14cf55 --- (Obligatory "aaah it looks different" rant: I tried getting used to it, but after a week or two, I still think overscroll feels /wrong/ with touchpads... Maybe it's the technical problems: the blue overlay sometimes gets stuck for a second or two, since the "kinetic scroll" feature keeps sending scroll events even though I've released my finger already. Or maybe it's just too blue. Idk.)
Created attachment 290524 [details] [review] Adwaita: theme overscroll edges on backdrop state It was resulting in fully opaque backgrounds when rendering the overshoot gradient. So ensure the :backdrop state gets the same gradient.
(In reply to comment #0) > (Obligatory "aaah it looks different" rant: I tried getting used to it, but > after a week or two, I still think overscroll feels /wrong/ with touchpads... > Maybe it's the technical problems: the blue overlay sometimes gets stuck for a > second or two, since the "kinetic scroll" feature keeps sending scroll events > even though I've released my finger already. Or maybe it's just too blue. Idk.) FWIW, the interferences with the kinetic scrolling feature in the synaptics driver are being discussed in bug #739944
Overshoot is basically not styled yet, the main problem there is that the overshoot shouldn't affect the slider. The patch cures the opaque background which shouldn't indeed be there, but the other problem is equally ugly or even worse (since I can't fix it by the theme mostly :-)), anyway feel free to commit (I'll probably go over that tho).
The inherited background bug is fixed with overshoot style landing, shall we move this bug to gtkscrolledwindow for the other issue?
Just checked, the other bug seems gone, closing.