3 ms·
I get the argument that fully custom scroll bars aren’t great for accessibility in many cases. However, the default behavior out of the browser or OS is pretty
by sfvisser 3y ago
I get the argument that fully custom scroll bars aren’t great for accessibility in many cases. However, the default behavior out of the browser or OS is pretty terrible in many cases as well.
Scroll bars popping in and out of existence awkwardly reflowing elements around it. Tiny unusable 30px wide horizontal scroll bars inside an input element because an element overflows 0.7px due to font size rounding issues or what not.
Default scroll bars are great for documents, but pretty terrible mostly for slightly more complicated UIs where a lot of info is displayed in small area.
- Sakos 3y agoI recently discovered to my dismay that Firefox uses Windows 11's setting for whether to hide the scroll bar. And it's hidden by default. Though FF is happy to hide them by default on its own anyway. I can't imagine how this is a good thing for end users for whom computers are already unpredictable and difficult to understand. Modern UX is a nightmare.
- donkeybeer 3y agogtk has forced overlay scrollbars now. Its possible to enable normal scrollbars again with a flag right now, but for how long? edit: they are removing the flag from gtk 4: https://bugzilla.gnome.org/show_bug.cgi?id=790677#c6 https://bugzilla.gnome.org/show_bug.cgi?id=790677#c6 gtk is effectively a gnome project now, and we all know gnome's attitude toward design and users.
- JohnFen 3y agoThere's a lot to dislike in GTK 4. I'm hoping that it gets used by fewer applications.