Web developers: we are going to go out of our way to hide the scrollbars!
-
-
-
@rysiek Honestly I just don’t like scrollbars and turn them off, but, like, I’m the user, I should be able to turn them off. Or on. Webdev (and Desktop Dev, because we’ve somehow regressed to be less capable than Windows 3.1) need to be hit with the User Sovereignty Stick.
@lightspill @rysiek We should also be able to keep them always visible, and control the thickness.
I totally get why people don't like the look of the scrollbars of the 90s, but that should be an option for those who need that (either due to vision issues, trouble using the newer style, or just personal preference)
-
Web developers: we are going to go out of our way to hide the scrollbars!
Users: but that makes it difficult to know how much of the text is left to read!
Web developers: don't worry, we'll add a non-standard UI element that signals this in some non-obvious, weird way!
@rysiek do you believe that I considered adding scrollbars to a slides presentation interface I'm developing? I just didn't do that because it would look too distracting (well, at least depending on the implementation, I can still look into that)
-
Web developers: we are going to go out of our way to hide the scrollbars!
Users: but that makes it difficult to know how much of the text is left to read!
Web developers: don't worry, we'll add a non-standard UI element that signals this in some non-obvious, weird way!
@rysiek That's the secret, Cap. I only implement infinite scrolling.
-
Web developers: we are going to go out of our way to hide the scrollbars!
Users: but that makes it difficult to know how much of the text is left to read!
Web developers: don't worry, we'll add a non-standard UI element that signals this in some non-obvious, weird way!
@rysiek well I still see double scroll at times still, so that can give some balance
-
-
-
@libewa @rysiek Prior to React, even stuff like Facebook followed the document model, where the document is semantic and the AJAX stuff just updates the semantic document.
React is what ruined the web with the despicable ideological position that the primacy of the document model is a bad thing and that you're supposed to write everything as an "application" that "renders" to the DOM.
-
Web developers: we are going to go out of our way to hide the scrollbars!
Users: but that makes it difficult to know how much of the text is left to read!
Web developers: don't worry, we'll add a non-standard UI element that signals this in some non-obvious, weird way!
@rysiek
GUI developers of Android, Windows since 7 (esp 10 & 11), & especially browsers (Mozilla has lost plot) are total abusive morons.
Using Mate with customised theme based on Server 2003, customised Thunderbird (fairly sane) and customised Firefox (has scrollbars but barely sane).
Also the active Tab should connect to active document. Are these folk deliberately trying to confuse & reduce productivity?
Text too grey & background too grey. No wonder people going back to DOS / Blackboard. -
@libewa @rysiek Prior to React, even stuff like Facebook followed the document model, where the document is semantic and the AJAX stuff just updates the semantic document.
React is what ruined the web with the despicable ideological position that the primacy of the document model is a bad thing and that you're supposed to write everything as an "application" that "renders" to the DOM.
-
@lightspill @rysiek We should also be able to keep them always visible, and control the thickness.
I totally get why people don't like the look of the scrollbars of the 90s, but that should be an option for those who need that (either due to vision issues, trouble using the newer style, or just personal preference)
@korgie @lightspill @rysiek fuckin love the scrollbars of the 90s
-
Web developers: we are going to go out of our way to hide the scrollbars!
Users: but that makes it difficult to know how much of the text is left to read!
Web developers: don't worry, we'll add a non-standard UI element that signals this in some non-obvious, weird way!
@rysiek we'll get to it as soon as we re-implement all basic form functionality in JavaScript.
-
@rysiek
yes.. we want scrollbars back! leave scrollbars alone!@bituur_esztreym @rysiek And CONSISTENT bloody scrollbars in terms of both function and appearance!
The browser sorts out the scrollbars on the basis of the preferences set by the user in the OS GUI.
-
Web developers: we are going to go out of our way to hide the scrollbars!
Users: but that makes it difficult to know how much of the text is left to read!
Web developers: don't worry, we'll add a non-standard UI element that signals this in some non-obvious, weird way!
@rysiek My bigger gripe with "disappearing scrollbars" is that they can make it very hard to scroll if you are not using either a touchscreen or a mouse with a scroll wheel. If you have to actually click the scrollbar with your cursor then good luck finding it ...
-
Web developers: we are going to go out of our way to hide the scrollbars!
Users: but that makes it difficult to know how much of the text is left to read!
Web developers: don't worry, we'll add a non-standard UI element that signals this in some non-obvious, weird way!
@rysiek I mean I literally did that to my emacs my alfernative is line numbers and a fraction of current line vs. total # lines. But I see how the difference is me deciding to walk barefoot and someone stealing all your shoes.
-
@korgie @lightspill @rysiek fuckin love the scrollbars of the 90s
@maypop_neocities @korgie @lightspill
Function over style.
-
@rysiek That's the secret, Cap. I only implement infinite scrolling.
@johnduggins "hail Hydra"?
-
@rysiek Honestly I just don’t like scrollbars and turn them off, but, like, I’m the user, I should be able to turn them off. Or on. Webdev (and Desktop Dev, because we’ve somehow regressed to be less capable than Windows 3.1) need to be hit with the User Sovereignty Stick.
@lightspill @rysiek Computers Commandments number one: Thou shalt not act as if thou knoweth better than thy user what thy user wants.
-
@ailurocrat @dalias @libewa partially, yes. But there were scores of web developers that should have known better, and yet helped implement this.
This is also on them.
