6 ms·
Infinite scrolling is universally bad for one, very simple reason: It breaks the scroll bar. One of the purposes of a scroll bar is to indicate how long (and/o
by Dalewyn 4y ago
Infinite scrolling is universally bad for one, very simple reason: It breaks the scroll bar.
One of the purposes of a scroll bar is to indicate how long (and/or wide) some piece of content is relative to your window. Another purpose is to indicate your current X/Y position within some piece of content.
Both of those purposes are completely broken with the use of infinite scrolling, because the length (and/or width) of the content keeps changing (increasing) and thus your position in that content also keeps changing.
I shouldn't have to explain how terrible this is from both accessibility and simple practicality standpoints.
- nonameiguess 4y agoNot only this, but every time it happens I have to wonder how it is that designers have never tried to actually use the scrollbar, getting to the bottom only to have it double in length, the placekeeper jumps out from underneath your cursor, the scrollbar then detects your cursor, and bam, you just skipped half the content without meaning to and it is virtually impossible to get back to where you were. This gets even worse when it isn't a list of entries you're reading but a single very long article or comment thread that should have just been paginated to begin with. It seems entirely motivated by a basic laziness of not wanting to create separate mobile and non-mobile views and defaulting everything to mobile-friendly even if it destroys the browsing experience of people using ordinary desktops and laptops.
- spookthesunset 4y agoNot maintaining a separate site for mobile and desktop isn’t lazy. Having two separate interfaces is not at all easy and it has its own set of trade offs. For example with two sites you now have two URLs and need to figure out which experience a browser should actually see. If I’m on a desktop and somebody sends me a mobile link, which page should I see?
- criley2 4y agoI have seen infinite scroll paradigms that simply load the next bit of content, causing the page to elongate, causing the bar to shrink and reposition. This is fine to me as the bar remains in exact sync with the document. I also think the scroll bar is an entirely desktop tool, and as infinite scrolling most benefits mobile, this is a moot point. Nobody on mobile uses the scroll bar. Personally, as a middle-click-and-hold'er, I do not use the scroll bar. I just went through my pages and frankly I'm surprised how the bar looks. I honestly never look at it or use it. As this article demonstrates the scrolling on mobile as well, I have to point out that your complaints are sadly more of edge cases w.r.t. to the products we're making for the general public.
- d0gbread 4y agoI use the scrollbar on mobile. It's a way to quickly navigate to a section of a particularly large document that would take tons of swiping. Not a frequent use case but an absolute necessity on occasion.
- criley2 4y agoInteresting, none of my mobile browsers even have a scroll bar.
- Wowfunhappy 4y agoAn autohiding scroll bar is still a scroll bar.
- criley2 4y agoI legitimately cannot get Chrome for Android to show a scroll bar under any circumstance. Android 13 / pixel 6 pro / Chrome, there is simply no scroll bar on any page no matter what. EDIT: Ah! I see it! I have a curved screen and the 1 px thin "bar" is only on the curved edge of the screen which catches the light and isn't visible. Fair enough.
- Wowfunhappy 4y agoWow! Okay, well that's dumb, never mind then!
- chrisseaton 4y ago> One of the purposes of a scroll bar is to indicate how long (and/or wide) some piece of content is relative to your window. Another purpose is to indicate your current X/Y position within some piece of content. Seems fine to me? New content is appended, so the length and your position changes. Scroll bar reflects what’s going on. What’s the problem?
- lelandfe 4y agoYeah, I'll bite. How is a growing scrollbar bad for accessibility? Why is an understanding of how long a page is an accessibility concern?
- Dalewyn 4y agoBecause not everyone has the hand-eye coordination and/or motor skills to keep track of an arbitrarily changing scroll bar, particularly the elderly and the disabled. An accurate and consistent scroll bar is a valuable navigation tool, please don't break it.
- chrisseaton 4y agoWhy do you need to coordinate your hand and eye to use a scroll bar? Don’t you use touch to scroll or a scroll wheel?
- Dalewyn 4y agoClicking/touching the scroll bar and dragging it directly is a valid way of using a scroll bar. Especially for people who come from a time when mice didn't have scroll wheels, clicking and dragging the scroll bar itself predates the convenience of whole-screen dragging (touch) and flicking the scroll wheel. Dragging the scroll bar has its benefits over touch/wheel too: It allows for quicker, longer distance travel with fewer (and in the sense that you just move your arm, also simpler) movements.
- lelandfe 4y agoHm. Do the the elderly and the disabled keep track of the scroll bar length? Does it getting longer actually confuse people? I'm not convinced this is as important of a thing. Opening modals changes the scrollbar length. Opening accordions do too. The scrollbar doesn't "break" when content is added to a page, it just adjusts accordingly. It seems like this is all good, expected behavior; not an a11y concern.
- mananaysiempre 4y agoOn one hand, yes, I agree. On the other hand, it seems to me that this is partly the fault of the scrollbar as an idea. How do you show the current position in a document for which, for one reason or another, you cannot instantly compute the visible height? I still remember an Android PDF viewer which would run through every page of a 2000-page document to get the page dimensions before displaying anything. (From what I can see, modern viewers display the first page instantly by accepting being caught in their lie when a PDF has pages of wildly varying size.) Even a gigabyte of Unicode plain text with no line breaks in a proportional font is a serious problem. I don’t think we can special-case network streaming here (although it’s not unimportant either).
- RunSet 4y ago> How do you show the current position in a document for which, for one reason or another, you cannot instantly compute the visible height? Perhaps by not "instantly" displaying the document- that is, displaying it before you are able to display its scrollbar.
- kevin_thibedeau 4y agoScrollbars can be dynamically updated as the content is processed. This is also a distinct advantage of a proportional sized scollbar elevator like those in Windows since the elevator shrinks to its final size rather then starting at a small fixed size and shifting around.
- 9dev 4y agoBut why on earth would I want to wait for a document to open, just so the height of the scrollbar is accurate when I see it first..? That is such a minor detail when viewing a document. Maybe the metaphor of the scrollbar is just a bad one?
- plugin-baby 4y agoOr just imperfect, but often useful?
- seydor 4y agoIt also breaks the "virtual scrollbar". if you reload the page you have to start all over
- eloisius 4y agoThis is the killer for me. I’ve gone from loving GitHub to hating it for this one quirk. When you reload the page while viewing a PR, you invariably land at some random spot instead of where you were.
- Wowfunhappy 4y agoThis is my primary issue with infinite scrolling. However, I wonder if it’s mostly a problem with today’s web browsers. Heck—maybe it’s not even browsers, but websites. I’m pretty sure a website could change the URL as you scroll, so if the page is reloaded (or bookmarked, etc) you’re brought back to where you left off. I usually dislike it when websites mess with URLs, but this seems like an excellent use case!
- seydor 4y agoeven if the website did re-start where you left off (difficult), what if you scroll backwards? When you send a link, should it point to the page that you scrolled to, or to the beginning of the list? How many items before/after should load? These arise solely because people chose to reinvent a browser -in-the-browser. With pagination we dont have these issues, the link points to a specific results page, uniquely.
- marginalia_nu 4y agoYou can still have weird issues with pagination if the data set you're paging through is mutable. Reddit used to struggle with this back in the day. The way they did pagination was to say "show the next page after id postId=xyz123". Since the algorithm kept re-sorting the posts on the front page, the content moved around quite a lot and you'd see the same things re-appearing on page after page, and sometimes post xyz123 was deleted and then everything broke.
- rendaw 4y agoThat's like claiming every data collection should have a reasonably limited length. Even if that were true, scrollbars in general break when the data gets too large (a pixel of screen movement jumps pages of data) not to mention browser layout performance, memory requirements, etc. Pagination doesn't work either, because data can shift and you get repeated elements (if the page size is less than the remaining data when moving back to the start) or else truncated pages, or you start on page 10 and move backwards to page -3 before reaching the start. If you jump to a particular element, it requires you to know the absolute offset of all data to calculate page numbers correctly, which when jumping and filtering a large table might be a significant performance cost. Plus it breaks up content - if you're looking at chat history for example, often related messages are broken up into several smaller messages. Having one message on page 10 and the remainder on page 11 would be a terrible experience. Don't blame this on designers, infinite scroll has been around (apparently?) almost 20 years now. Browsers still don't have an accessible solution despite the ubiquity of this pattern today - browser devs are to blame.
- Naomarik 4y agoI completely agree with you so I wrote one awhile back that doesn't break the scrollbar and also returns you to where you were on browser back. It's not perfect but I don't really care to improve it and no one has had any complaints. Check it out here: https://sayartii.com/search https://sayartii.com/search
- lelandfe 4y agoThis doesn't appear to be infinite scrolling. I can scroll to the bottom of the list with Cmd-Down. It just appears you're lazily rendering results. N.b. it's incredibly slow, because it has to load every batch above the scroll position first. Try going to the bottom of the page and seeing how long it takes for results to render.
- gampleman 4y agoI think this depends on what kind of content you are scrolling. If you know how many items there are and all the items have the same height, then you can simply set the height of your container for the scrollbar to be accurate. Furthermore you can listen to the scroll event and load the correct items if the user uses the scrollbar to jump to a particular spot. So I think the bigger problem is a) people being lazy and not implementing this properly b) using this pattern where the preconditions don’t hold.
- LinAGKar 4y agoIt also means that when dragging the scroll bar, the page will suddenly jump when it loads in more content
- Findecanor 4y agoThat sounds like a deficient implementation for a scroll bar widget, more than anything else.
- chrisweekly 4y agoInfinite scrolling also immediately destroys the concept of a footer. IME (building websites/apps for a living since 1998) footers are an excellent and underutilized place to put large amounts of supporting materials, expanded navigation links and related affordances. Consider the absurdity of infinite scrolling in a page with a layout containing a footer that can never be reached (perhaps briefly glimpsed before being pushed out of sight).
- Wowfunhappy 4y agoI mean, the obvious solution to this problem is to not have both footers and infinite scrolling; you have to pick one.
- SnowHill9902 4y agoSome datasets don’t have a natural order so a position is arbitrary. You just want to iterate over all of it in some useful sequence without arbitrary seek.
- psnehanshu 4y agoOn mobile devices the scroll bar is barely visible. So this is a non-issue for mobile.
- spookthesunset 4y agoI don’t even think you can grab the scroll bar and move around on iOS… though I kinda remember you being able to way back in the day…
- djcannabiz 4y agoyou definitely can, try long pressing on it
- amelius 4y ago> Infinite scrolling is universally bad for one, very simple reason: It breaks the scroll bar. It also breaks the back button, in all implementations I have seen so far.
- spookthesunset 4y agoWhat is “back” on a dynamic page like Reddit, Facebook or even this site? If “back” means “show me exactly what I last saw” it might mean you are showing stale data. I dunno. Shit ain’t easy once you think about it for a while. If all you have is a static unchanging set of items… might as well just use old school pagination! At least in my opinion. It’s when the list of items is constantly changing that things get interesting.
- jandrese 4y agoIt might be stale, but it's the content I want to see. The F5 key still works if I care about getting it up to date.
- melagonster 4y agoe.g. FB create a search for their website, apparently this is because browser's don't work like user's need. sometimes, I find there are 3 different search box on one FB page, I should remember which one is it...
- xorcist 4y agoIt also breaks the find button. The item you wanted to search might get unloaded, or not loaded yet, in some bizarre attempt at optimization when the javascript library resposible is an order of magnitude larger than the actual content anyway. My phone has gigabytes of memory. If you want to present five hundred items in a web shop, just list them and do not bother with any type of pagination, invisible or otherwise.
- spookthesunset 4y agoGigabytes of memory yes but there is load time and render time too. And rendering a 120mb payload of items and their thumbnails before I can even view the top of the page seems… not the best user experience. I don’t think there is an easy answer here. All options have some trade offs.
- xorcist 4y agoThat is not how browsers work. The browser will render the viewport immediately, long before the page has loaded. It will also load the visible thumbnails first, unless made impossible by complicated markup of course. Otherwise surfing the web on dialup in 1996 would have been intolerable.
- _cd 4y agoTypically when I serialize data for #index endpoints I return much slimmer payloads than I do in #show endpoints. I recognize that 120mb was an extreme, but you should be able to serialize lists of 500+ items into well under 1mb, with enough data to render your list view thumbnails/links. I always thought the infinite scroll pattern was designed for analytics purposes. So that you can track user engagement. Not because technology constraints necessitated it or that it was a good user experience.
- NLPlatypus 4y agoJust have JS track where the user is?
- shadowgovt 4y ago
- kordlessagain 4y agoInfinite scrolling is bad because it has ZERO respect for document boundaries. An "infinite" document is a travesty.
- dalmo3 4y agoDefine document. Is a log file a document? How would you render a log file in real time without some sort of streaming (i.e. infinite scrolling)?
- tsimionescu 4y agotail -f considered harmful?
- dreamlifelike 4y agoThis is like saying that electric cars are universally bad because they break the MPG meter… Scroll position as measured by a scroll bar doesn’t make sense for an infinite (or indefinite) document. That doesn’t make an infinite document bad.
- dimal 4y agoIt is possible to implement infinite scrolling and maintain the scrollbar height if you know the full number of results you’re going to scroll through and the height of each element (both of which are usually knowable). You simply set the scroller div to elementCount * numElements regardless of the number of elements. Most libraries that provide infinite scrolling do this.
- rnk 4y agoJust don't ever use it.
- grogers 4y agoScrollbar hasn't been useful for that (at least for me) ever since websites started putting comments after the content (e.g. article, blog)
- lupire 4y agoExpand your perspective: What does scroll bar mean when you have no intention of ever scrolling all the content? "Infinite" scroll isn't breaking anything, the content all broke scrolling inherently.
- mikotodomo 4y ago> One of the purposes of a scroll bar is to indicate how long (and/or wide) some piece of content is relative to your window And how would you do that when there is infinite scroll?