GNOME Bugzilla – Bug 746114
Scrollbars of HTML areas are too wide and not consistent with standard scrollbars
Last modified: 2015-03-14 02:41:16 UTC
Created attachment 299241 [details] Comparison of scrollbars Not sure if I'm filing it to the right component, but I don't know where else to file it. Scrollbars of HTML areas (either it's GTK-3 Firefox, or webkitgtk in Web or in GNOME Online accounts) are two wide and different from standard GTK3 scrollbars. It doesn't look very well especially on websites where you have several such scrollbars, it also takes a sizable amount of horizontal pixels. In 3.14, those scrollbars were consistent with other GTK-3 applications. The new overlay scrollbars should be used. And if they can't, at least scrollbars with the same width. See the attached screenshot to see the difference.
yeah, nothing we can fix from the gtk side - the scrollbars are the responsibility of the browser / web content. I'll move this bug to epiphany, but it may end up getting closed there...
Hi, this is https://bugs.webkit.org/show_bug.cgi?id=140800
(In reply to Michael Catanzaro from comment #2) > Hi, this is https://bugs.webkit.org/show_bug.cgi?id=140800 Although Firefox is a different matter. Matthias will let them know.
(In reply to Michael Catanzaro from comment #3) > (In reply to Michael Catanzaro from comment #2) > > Hi, this is https://bugs.webkit.org/show_bug.cgi?id=140800 > > Although Firefox is a different matter. Matthias will let them know. I can let them know myself. It just stroke me that it looked the same both in Firefox and Epiphany, so I thought it was rendered by GTK. But apparently it's the changes in Adwaita that broke the rendering of scrollbars in browsers.
Yes. Matthias, if you know what changed and can provide guidance as to what to do that won't break how we handle non-Adwaita themes, that would be helpful.
I filed a bug against Firefox: https://bugzilla.redhat.com/show_bug.cgi?id=1201527 But some guidance would be appreciated by FF devels I suppose.
*** Bug 746190 has been marked as a duplicate of this bug. ***