14 ms·
Scrolling on the web: A primer
- afandian 10y agoI wish people who made webpages trusted browsers to scroll. The number of sites that play with the scroll speed and consistency by hijacking scroll events makes me doubt whether the designers spare a passing thought for usability. Scrolling is one of those things that (in my opinion) get calibrated in the brain for hand-eye co-ordination. Which is why (again IMHO) there are religious wars fought over, for example, Apple's trackpads. This stuff is important. It can be a jarring experience when scrolling suddenly doesn't work. Flip side is, I'm sure some people don't care. There's nothing more annoying than a web designer saying "I know better than you" and re-implementing features. Because they're usually wrong. EDIT: Would people accept it if each webpage re-adjusted your mouse pointer speed and acceleration? Is there any difference between one mouse function and another? Why do web designers think they have the right?
- DiThi 10y agoI wish the same thing, but for desktop applications too. There are some that implement their own scroll and it's the most annoying thing ever, because it makes the scroll bar unusable. As the article point out, it's vastly different than scroll wheel, touch and keys. Scroll bars provides 3 different scroll methods: - Click and drag scroll thingy. The most used method, but sometimes misunderstood. It should scroll only as much as you moved the mouse. It wreaks havoc with endless scroll pages. - Click on the bar outside the thingy. This used to be equivalent to pgdown/pgup. It was the method I used the most, and I was infuriated countless times when it behave differently: on some platforms it means "go here". - Arrow buttons. Not very useful and virtually extinct at this point.
- mariusmg 10y agoYou forgot Space key which is by far the best way when reading long texts.
- afandian 10y agoAgreed. I have a great Apple mouse and trackpad. But I still use space when scrolling. Lots of know-it-all web developers hijack scrolling and unsurprisingly don't know that you can scroll with space. The OS developers have thought about accessibility.
- pimlottc 10y agoNear-ubiquitous floating headers (and even footers) have made full-page spacebar scrolling practically useless on most pages for me now, at least under Chrome on OSX. You always have to scroll back a little bit to see a line or two of content.
- meej 10y agoThis bookmarklet helps a lot with this: https://alisdair.mcdiarmid.org/kill-sticky-headers/ https://alisdair.mcdiarmid.org/kill-sticky-headers/ What's frustrating is that this is a solvable problem. I've seen sites that have fixed it, and fixed it well. But they are vanishingly rare. So I will just keep killing their sticky headers and footers...
- pimlottc 10y agoYou're right, some sites manage to do it without breaking full page scrolling. One of these days I'd like to sit down and figure out the specifics (of both right and wrong ways) and write a good comprehensive medium post with clear instructions on doing persistent headers correctly. Of course if someone else beats me to it, that's fine too...
- boomlinde 10y agoThe space key is not part of the scroll bar, so in the context of listing ways that a scroll bar can be used it wasn't forgotten but simply left out.
- myfonj 10y ago- Click and hold outside the thingy usually performs consecutive page jumps to the point (Firefox, Chrome) Few omitted means to scroll - hold middle mouse button and drag (this usually works well sideways and in case no scroll bar is present) - spacebar / shift+spacebar, pgUp / pgDn, home / end - and FMoPW most importantly clicking the arrows in the scroll bar. For "us" this seems almost uncomprehensible, but I regularly see users perform scolling this way. For example my wife with track pad (yes, it is capable of two finger gestures), and my mother even with mouse with scroll wheel, until recently. No wonder, discoverability of that action is way above all that abstract "dragging", "swinging" and "pressing" concepts without direct visual clue.
- binaryjason 10y agoshift+spacebar, you just changed my way scrolling on Mac keyboard
- chrisbuc 10y agoArrow buttons. I pretty much only use arrow buttons to scroll screens of text into my eyeline. I get really annoyed when arrow buttons are overloaded to tab between screen elements instead of scrolling (my online banking site, I'm looking at you!)
- DiThi 10y agoI mean the buttons in the GUI scroll bar, that have little arrows or triangles in them. They're way too small and too far apart to be used effectively. For that reason some UI toolkits had both buttons together at the bottom.
- codedokode 10y agoCustom scrollbar implementations also often ignore scrolling speed set in OS's settings.
- shultays 10y agoThere was also right clicking on bar background and clicking "scroll here" on the menu. Imagine how many times this feature is used in whole history!
- LoSboccacc 10y agomy only issue with scrolling is how the the bar looks > https://i.imgur.com/rgIbdur.png https://i.imgur.com/rgIbdur.png it comes in only one color variant, it's inconsistently looking across browser, takes a lot of space, especially for scrolling narrow elements, it has low contrast so it doesn't even do a good job accessibility wise etc. go to a site like Bulgari's and bam, custom scroller, precisely for this reason https://i.imgur.com/T3Yasht.png https://i.imgur.com/T3Yasht.png you'll notice the page scroller is untouched, because it doesn't contrast with the page style, being a browser element, but the inside page scroller would sucks. you gonna argue with them they have to design their website style to accomodate the gray slate slab of vintage scrollers?
- Jaruzel 10y agoI recently discovered how Facebook do their fade-in thin scroll elements in the messenger[1] web app. They actually size the DIVs too wide by about 20+ pixels, then they alter the z-order so that the DIV edge (where the native scrollbar is) is hidden under another DIV (or over the window bounds). Then they overlay their own scroll bar element at the new visible edge of the DIV and hook it to the div scroll event. It's one of the worst CSS kludges I have ever seen. I don't know enough about cross browser compatibility though to know if there's a better way? -- [1] https://www.messenger.com https://www.messenger.com
- taejavu 10y agoKludge it may be, but if it allows them to have custom scrollbars without replacing native scrolling, it's absolutely the lesser evil.
- Flow 10y agoI've set OS X to always show the scroll bars, and wondered why they disappear on Facebook. Their custom scroll bar looks identical to the native one. The whole thing they made feels pointless and user hostile.
- 10y ago
- anamoulous 10y ago> There's nothing more annoying than a web designer saying "I know better than you" and re-implementing features. Because they're usually wrong. It's not just that they are saying "I know better than you", they are saying they know better than HCI teams that have spent years tuning interfaces in response to actual research and testing. Most of the web and app designers I've worked with have never watched a person use their designs, much less considered their work in the context of the entire OS experience.
- iMark 10y agoI'll never forget the despair I felt when I started a new job and sat down with the designer of the site we were to be working on. She told me "Our site isn't going to work like any other website." She was right. It didn't. The whole thing was canned six months later.
- smacktoward 10y agoThis is a battle I've fought a zillion times. It's just so hard for some designers, who are used to a world where originality is a good thing, to understand that in UX originality is a liability.
- mozumder 10y agoThere are 15-year old bugs in Firefox on scrollbar designs that are fixed under Chrome/Webkit. Often times custom scrolling is used to fix that.
- jdiez17 10y agoWebpages that mess with scroll behaviour invariably annoy me as much as those that autoplay videos, open popups, etc. I just instinctively ctrl-w that shit immediately.
- dredmorbius 10y agoI've been adding them to my router firewall as DNS blackholes as well. Just for good measure
- SonicSoul 10y agoThis is a pet peeve of mine too and I agree with all your points. But I think more often than not, such custom scrolling may happen as a result of trying to control something else, like some infinite scroll with virtualization that would normally start shifting elements and make the scrollbar behave funny. not defending this pattern, I just don't think people fuck with the scrollbar just to make it "better". they probably try to make it as close to original as they can which of will of course be, nothing like the original :)
- tambourine_man 10y agoScroll highjacking can be done to avoid partial content being displayed on the screen. You know those pages with several 100% height slides? They don't look as nice if there's a bit of the previous one showing at the top or the next one at the bottom. But yeah, it sucks, we all agree with that. We need this to be done in CSS, something like body { scroll-step : 100%; } What I don't understand is scroll highjacking in something like Google AMP. It replicates the browsers default behavior, only poorly. No tap the menu bar to scroll to the top, motion sickness inducing acceleration, etc
- afandian 10y agoSurely the navigation should be decoupled from scrolling. I think this happens because people try to shoe-horn multiple pages into one page. IMHO these should be separate pages, not one page with pseudo-subpage content. You could use mouse events, or click buttons, or touch events to navigate between them. Perhaps this comes out of the hinterland between touchscreen scrolling and gesturing. What if I want to zoom in or out on the slide for reasons of accessibility?
- accountface 10y agoI agree with you — BUT, I have conducted a fair amount of user tests where someone will not scroll. It's often an older demographic, but I've seen 30 year olds fall into it as well. So it's not always a designer saying "I know better than you." I do think that they're going about solving the problem the wrong way though. Your design should on its own encourage scrolling by making it obvious that additional content exists (avoiding so-called "false floors") — it can be harder to do this than unchanging your design and suggesting scrolljacking, which is why I think we see it so often.
- afandian 10y agoI think that's a different issue. If people don't know they need to scroll (your false floor example), that's a failing of the visual language, so it's entirely appropriate to put an explicit message "you can scroll" to make up for the failure of visual language. I'm talking about what happens when you actually do scroll. In my experience those seem to the same sites that are visually confusing are the ones that re-program your scroll down as a page-down...
- retube 10y agoyeah I find any cursor hijacking to be very frustrating, and always results in a "worse" user experience. A big one is Google search results, where a down arrow increments a step through the result list, and not an immediate page scroll.
- lloeki 10y ago> trusted browsers to scroll This is especially egregious on mobile, where not only they implement scrolling badly in a way that only vaguely matches a single device/os (with terrible performance) and is completely off on others, but also feel compelled to hijack scrolling for "creative"† navigation, like swipe left/right to move across articles, which gets triggered every time you scroll downward but ever so slightly sideways. Like, I'm on a bus and actually holding the phone, so don't zap me to an unrelated article I don't care about on each encountered pothole please. † at least as creative as the number of expletives I'm thinking about every single time such an abomination of an interaction triggers.
- eloisius 10y agoWith the new AMP articles, Google News has become almost unusable to me for this reason. I used to love it, but now the experience is all janky and I constantly end up navigating to some other article instead of backwards when I use iOS' swipe back gesture.
- CaptSpify 10y ago> There's nothing more annoying than a web designer saying "I know better than you" and re-implementing features. Because they're usually wrong. This is my problem with overly designed interfaces in general. Your website is not a special snowflake. It doesn't need a new way to interact, it needs consistency with other sites.
- xorcist 10y agoDoes it matter anymore? For those of us who use the scroll bar for its intended purpose, everything broke with the single page fad. Now so much of the web doesn't scroll anymore that I've re-trained myself on the arrow keys. That mostly works, until they set keyboard focus too. Even newspapers now load some entirely different article when I've read half way through one, just in case I want to feast my eyes on something unrelated when I'm done. I'm just sitting this one out. It'll pass.
- scoates 10y agoIn case you haven't seen it (didn't notice it linked in the replies): http://codepen.io/gunderson/full/GJJPpV/ http://codepen.io/gunderson/full/GJJPpV/
- helb 10y agoSomewhat related: Chrome plugin to stop scroll hijacking – https://joshbalfour.github.io/disable-scroll-jacking/ https://joshbalfour.github.io/disable-scroll-jacking/
- deleted 10y ago[deleted]
- teknopaul 10y agopage is not readable in Opera mini. Lolz.
- nuclx 10y agoI'm happy, if I'm able to scroll at all. Hate the trend of dynamically loading content when scrolling down.
- username223 10y ago> Hate the trend of dynamically loading content when scrolling down. Yep, this sucks. Typical use case: I load a few articles in background tabs to read later offline. Too late, I realize they either load dynamically, or have a useless periodic refresh (I'm looking at you, NY Times), so they're useless when I go to read them. I've mostly learned to quickly scroll all the way through tabs to make sure they're loaded, but this is a poor solution to a self-imposed problem (too-heavy pages).
- dredmorbius 10y agoOpen to archive.is or Internet Archive. Pocket or similar apps are another option, though most have their own fatal limitations.
- dredmorbius 10y agoOpen to archive.is or Internet Archive. Pocket or similar apps are another option, though most have their own fatal limitations.
- modeless 10y agoBack in the day browsers competed over user friendly features like popup blockers, even though that technically breaks a web API. Today browsers are so terrified of breaking a web API that they have allowed the mobile web to become a cesspool. Browsing most sites has become intolerable, the more modern the worse. Scrolling freezes for seconds at a time, whole pages jump up and down constantly while you read, scroll-hijacking ads interrupt you, fixed position headers obscure half the page and appear/disappear at random, "mobile-friendly" sites are more often than not worse than desktop sites even on mobile (plus they break deep links), and I can't be the only one who's noticed that even the old popup blockers have stopped working!
- nkkollaw 10y agoI agree with you on performance, but how is the performance related to this: > Today browsers are so terrified of breaking a web API that they have allowed the mobile web to become a cesspool
- modeless 10y agoMost cases of bad scrolling performance could be fixed if browsers would accept some web API breakage and move scrolling to its own thread that JavaScript, layout, and image loading can't ever block.
- chongli 10y agoBrowsers outside the mainstream are still trying. I'm typing this on the Brave browser[0] and it's fantastic at dealing with those obnoxious sites. It has a built in ad blocker and total JavaScript blocking for a site is just 2 taps away. It's amazing how much smoother sites become when you've blocked all their anti-user shenanigans. [0] https://brave.com/ https://brave.com/
- JustSomeNobody 10y agoBecause more and more of them display nothing without js.
- 10y ago
- stupidcar 10y agoAnd yet there is still no way in CSS to, say, freeze a table header and make the body scrollable. Or freeze one column and make the rest scrollable. For all its advances, the web platform is still incredibly primitive in some areas.
- currysausage 10y agoYou mean position: sticky? [1] Yeah, that took way too long, leading to horrible JS implementations, but it's there now. [1] https://developer.mozilla.org/en-US/docs/Web/CSS/position#Sticky_positioning https://developer.mozilla.org/en-US/docs/Web/CSS/position#St...
- noir_lord 10y agoI can't wait for that to be supported but MS Edge currently doesn't support it (though it's under consideration).
- currysausage 10y agoWith an ever-declining IE/Edge market share, I usually rely on the principle of progressive enhancement and accept that certain non-essential features will only be available to users of modern web browsers (unless, of course, a specific project has an unusually high number of IE/Edge users, e.g. intranet applications).
- ry_ry 10y agoDeclining, but still non-trivial. We dropped IE10 support when we stopped doing IE9 a year or so ago because they both had similarly insignificant numbers, and the opportunity cost of supporting them was too high. IE11/Edge are also showing fairly similar numbers, which suggests edge uptake is slow, but even factoring in the extra hours, the bugs they generate (usually weird flex issues in both cases) we still effectively make more money by supporting them than not.
- 10y ago
- deleted 10y ago[deleted]
- RyanMcGreal 10y agoThere’s a curious anomaly, though: if you try to scroll using touch screen scrolling, the page happily moves up and down, even while JavaScript is blocking nearly everything else on the page. This also works for touch pad scrolling, mouse wheel scrolling, and click-and-drag scrolling (depending on your browser). Mouse wheel scrolling still works on Chrome but not on Firefox.
- nolanl 10y ago(Author of the post here.) It may depend on your OS or your Firefox version! :) I spoke with some Firefox folks after publishing this piece, and it turns out they've fixed some things in Firefox 52, notably for touch-enabled Windows laptops.
- onion2k 10y agoThis is a fantastic piece of technical writing. There's plenty of detail and pretty much no fluff. More of the same please Microsoft.
- noir_lord 10y agoI agree, it really is an excellent piece and I learnt a few things I didn't know.
- dualogy 10y ago> There's plenty of detail and pretty much no fluff. More of the same please Microsoft. It's par for the course with MS tech docs IMHO, well at least the bulk of their dev documentation. I even marvelled at the MSDN docs for the same reasons some 15 years ago as a freshman. I was relieved to see the same spirit in the "extensibility" articles at http://code.visualstudio.com/docs/ http://code.visualstudio.com/docs/ (compared to the huge furball of distributed-across-blogs-and-forums, incomplete, or dated equivalent for say Sublime..). Now. OS-wise and userland-wise I'm certainly no MS fan (and tend to stay as clear as is feasible), but as far as the entire developer ecosystem goes (except maybe SharePoint-related, that was quite the mess a few years back, dunno about today tho), it has been for ages and continues to be: near-on utopia!
- eduren 10y ago>except maybe SharePoint-related, that was quite the mess a few years back, dunno about today tho Ah, glad you mentioned that. I was about to say that Sharepoint (especially 2005-2010) felt woefully under documented when I worked with it. I think Sharepoint dev has gotten better since 2013 (the introduction of their app model), but I left that role before the company upgraded so I can't say for certain.
- anotheryou 10y agoWhat I really want for spacebar scrolling is this in working: https://greasyfork.org/en/scripts/20937-red-read-line https://greasyfork.org/en/scripts/20937-red-read-line An indicator on where the bottom of the screen scrolled to, so I don't need slow animations or incremental scrolls to find where I left off reading. (The linked script is not working on all pages and sometimes blocking klicks, I just threw it together to try if the Idea works. I think the principle works really really well.)
- narrowtux 10y agoIMHO this is only needed if the scrolling is not smooth like on mobile or macOS.
- anotheryou 10y agoEven for scrolling page-wise? Or you mean the keyboard is not needed when scrolling is smooth? (Die hard keyboard fans will tell you otherwise :) )
- jstimpfle 10y agoBold claim (not a professional webdesigner): Many problems with performance and usability would go away if people made more websites where the document is 100% width and height and contained boxes are individually scrolled. ("Like frames"). Basically, the way it's typically done when using desktop widget toolkits. But most websites are still made so that there is only one document-wide scrollbar.
- chuckdries 10y agoMaybe, but probably not for most sites. My 2 cents as a tudent/freelancer who's been working on a project that does weird shit with scrolling because it has to. The way I see it, most websites fall into two broad camps of layout and associated scroll behavior: 1. Articles 2. Dashboards You're either trying to present some kind of information as text like most news sites, forums, etc. or you're doing a "web app." It's really less "either-or" and more of a spectrum, but if we're talking about compartmentalizing an entire website into scrollable containers this is where things fall. For an article style website, you'd want either the entire page or the majority of the content on the site in a single scroll container. Perhaps you're a news site like Medium that has certain UI elements that persist during scroll. Normally you'd just position:fixed those elements, but let's say instead you decide to position your fixed nav and whatnot normally and instead scroll the article inside a box. You run into a few problems: 1. You don't get the benefit of compartmentalizing your scroll listeners because whatever blocks scrolling blocks whatever people care about anyway 2. Designs like this are really hard to get right. Positioning and sizing these elements is notoriously hard to fully test and easy to break. In mobile safari, for example, the showing or hiding of the UI is determined by scrolling the main page. Scrolling within a container does do this. Also Safari uses MacOS/iOS's native UI scrolling system, so scrolling really fast bounces back. However, your box may not bounce, the entire page will if they flick the box and there's still scroll velocity left when they get to the bottom. This bounce CAN affect the visible state of the UI and can really mess with innerHeight calculations. With multiple scrollable boxes on a page, dealing with touch input can be a huge pain. I'm sure you've seen websites that do this incorrectly, where things don't scroll like you think they do. Have you ever tried to scroll a page that had a poorly implemented map on it and scrolled the map instead? In fact, because of this behavior, early versions of mobile safari simply refused to scroll scrollable containers on drag. By default, it would only scroll the page itself and you had to drag with two fingers to scroll inside of Divs and Iframes. Most sites I browse fall into this camp. The second camp is dashboard UIs. The canonical way to do a dashboard with multiple scrollable elements is to do just that, which already has the optimization you suggested applied. However, a lot of designers these days actually try to design dashboards using the browser's native page scroll as much as they can. It turns out that there is a lot of complexity to that approach that makes development hard and breaks the user's expectation for how websites work. The story editor of the CMS we use at my college newspaper actually becomes unusable if you trigger the safari page bounce while a mouseover menu is open. They're in the middle of developing a new version, where the story is the page and the UI is position:fixed instead of everything being compartmentalized like you suggest, as it is now. Back to native scrolling. There's a lot you can do to help the browser along. The biggest thing you can do is utilize window.requestAnimationFrame(). Your function will be queued up and called when it is convenient for the browser, usually 60 times a second which is fast enough to render things smoothly without firing every time the onScroll event occurs, which can be hundreds of times a second on certain browsers. Check out the MDN Doc for an example of how to do this. https://developer.mozilla.org/en-US/docs/Web/Events/scroll https://developer.mozilla.org/en-US/docs/Web/Events/scroll
- barrystaes 10y agoI would think that "NOP" code like that example would be optimized out: setInterval(() => { var start = Date.now(); while (Date.now() - start < 500) {/* wheeeee! */} }, 1000);
- AlphaWeaver 10y agoJavascript doesn't by default do any optimization by removing or modifying code if you don't run the code through some sort of preprocessor or compiler.
- ygra 10y agoOnly it it can prove that Date.now() has no side-effects or that the loop actually ends. (And Date or Date.now() might not be the same things that are usually expected, since anything in JS can change.)
- bzbarsky 10y agoIt's not "NOP" code because it has an observable side-effect, unfortunately: time passing. This can be trivially observed with another interval timer at smaller resolution than 500ms.
- juiced 10y agoOfftopic, but how come, when I see this website is on windows.com, that I expect it to load slowly?
- m_fayer 10y agoThis is the kind of "accessible take on fundamentals that you might not have even realised were fundamentals" documentation that I'd like to see more of. It took me a few years of web development to even start thinking about just how, exactly, the concurrency model of the web functions.
- _pmf_ 10y agoMy favorite is dedicated mobile sites that do animations on scrolling.
- joshiefishbein 10y agoThe constant finger-pointing to the shortcomings of other browsers was getting particularly annoying — especially when IE and Edge are historically the lowest performing, late-to-the-game browsers. Nice article, but comically ironic.
- contextfree 10y agoIE/Edge has prioritized scrolling performance more than other browsers on Windows for a long time now (mainly because Microsoft cares more about touch on Windows than other browser vendors do).
- syphilis2 10y agoI feel that the mechanics of scrolling need to be reworked. I have to do a number of tweaks to get free scrolling to work as I'd like, as opposed to the default line-by-line type scrolling. Even line-by-line scrolling has issues, such as not being aligned with the lines of text or block elements on a web page. Scrolling ought to have different control options as well, say ^Scroll scrolls through paragraphs or headings.
- codedokode 10y agoThis can be implemented in a browser extension. And I don't think everybody needs scrolling through paragraphs.
- codedokode 10y agoIt looks like a poor design desicion made 20 years ago (that wheel event is synchronous and must be run before scrolling) leads to all major browsers code becoming unnecessary complicated. I think it would be better to discard that design and make a new event system that would be used with new pages (and don't waste developers' resources to optimize old pages). Maintaining compatibility is good, but at some point we need to stop and make a new design. By the way here are the things I'd like to get fixed too: - make a distinction between same-domain and cross-domain requests (use another HTTP method for cross-domain POST request) so all sites get XSRF vulnerability fixed - make cross-domain requests anonymous by default - make cookies unaccessible to Javascript by default - stop JS loading from blocking the page so we can put script tags in the header where it makes more sense - make as much events asynchronous as possible - fix keyboard events, key codes and mouse buttons numbers - make it impossible to change window.opener.location and windows.parent.location - add CSS rules to set width for a column in a table, not for cells - add error reporting so if some resource (like a script) fails to load the user gets a message that the page is broken
- iaml 10y agoThe situation here is IMO similar to Mozilla vs XUL, except when they actually decided to drop it a ton of people decided to drop firefox. I'm talking about compatibility in general here, not js scrolling specifically.
- wcummings 10y ago>Mozilla vs XUL What is this referring to (I know what Mozilla and XUL are, didn't know there was a tiff about it)?
- iaml 10y agoXUL will be dropped soon in favour of WebExtentions, and it doesn't offer as much flexibility as XUL. This means it won't be possible to create addons like tree-style tabs for example.
- makecheck 10y agoThe only thing worse than having a broken scrolling experience on mobile is imagining just how much extra data was wasted to download that useless script so that a crappy mobile experience could be had, and how much battery was wasted running the unnecessary script so that a crappy mobile experience could be had. There is complete priority inversion on the web and I am so sick of it; my device should have ample controls to obey ME and not the whims of some random site.
- romaniv 10y agoI'm not sure why anyone is using scrolling events for any standard websites at all. It's much easier to have a function on timer that detects the current viewport position and acts accordingly. The code is simpler, the performance is better, and it's way more future-proof.
- combatentropy 10y agoI prefer to scroll with the spacebar. Therefore fixed headers are the enemy (like in this story!).
- dredmorbius 10y agoThe first rule of fucking with scrollbars is you don't fuck with scrollbars. You don't set your scrollbar to fade out when not in use. O hai Pocket. Ficks that shite plz. You don't have an "untouchable" scrollbar. It's not merely a graphical decoration, it's a motherfucking control element. O hai Pocket.... Esp. your non-incremental-searchable tags list that takes me a full fucking minute to scroll up or down. You don't turn a vertical scroll action into a motherfucking horizontal scroll. I forget which academic article site that is, but I'm blackholing your ass on DNS next time I land there. You don't nuke the right-hand-side scrollbar, and replace it with a horizontal-across-the-top motherfucking stripe to indicate how far down the fucking page I've read. O hai Bloomsburgs. You don't have fixed headers and footers. Fuck that shit. Firefox Reader Mode fixes that, usually. Pocket is an alternative. You don't change the width, colour, buttons, or any other elements of stock scrollbars. I am too old to be too old for this shit.
- mustafabisic1 10y ago"User scrolls with two fingers on a touch pad" This was so weird for me at the beginning haha Always mixing up and down :D Anybody else had this problem?
- npolet 10y agoI really didn't have this issue when it became commonplace. It felt natural. Like a piece of paper sitting on a table. If i want to "scroll down" the paper by moving it up, i would touch the paper and move it up. Scroll down to move down feels completely wrong. In my head I understand that you're moving the 'viewport' down, but my brain is focused on the viewport's content, not the viewport itself. So my interactions should be with the content not the contents viewport. Not sure if that makes sense.