151–160 of 175 posts
Earlier quoted context omitted.
Um, no. Pagination absolutely makes things linkable. Again, details matter here, but it is easily solvable.
"Um, yes". As a catalog grows, past items get pushed to later pages making page-linking useless.
Maybe if you're linking to the page with the dragonfruit on it and a bunch of items get added between that and the banana it might be off by a page, but it'll be close enough to be useful.
Never; the time to use infinite scrolling is never . Specifically, infinite scrolling, where the remaining/invisible data is not loaded until getting towards the end of the loaded segment. For the visually impaired infinite scrolling breaks search and text-to-speach tools. A better solution is give the option to paginate with the set size, 25, 50, 1000, or whatever; or load the entire list in one shot.
After reading the comments and taking everyone's input, here are a couple of points: * infinite scrolling turns webpages into web apps yet not everyone likes or expects web apps; * infinite scrolling fails to tell people when they reached the end and this is frustrating; * infinite scrolling fails to tell people how far along they have consumed the content, or how far back is the top bar; * infinite scrolling breaks…
Earlier quoted context omitted.
Most of us take for granted the fact we are all still physically and mentally fit (and also know how to operate computers!). Inevitably though, age will catch up to us one day. Particularly for the elderly and disabled, but honestly pretty much anyone not familiar with using computers, elements of the user interface suddenly changing seemingly at random is extremely disruptive and disorienting. In the spirit of acces…
> eliminate such behaviour because being disrupted and disoriented like that is really unpleasant This appears to be postulation on your part rather than actual knowledge of accessibility needs. The specter of "visually changing things are bad" may hold some water (WCAG requirements do include things along those lines), but in order to discourage folks from using common web components I'd definitely need to see some…
I mean, this whole thread is rife with people telling stories of being terribly annoyed by the shenanigans that infinite scrolling causes. Including issues both involving the scroll bar as well as other forms of navigation that break down with infinite scrolling.
I'm sure you have also experienced moments of disorientation when something you were using (not necessarily infinite scrolling) suddenly decided to do something all on its own and left you to figure out what just happened.
Earlier quoted context omitted.
It 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.
It also breaks the “back” button. If you click on an item after significant scrolling, view the item, then click back, where are you? almost never where you were. Usually just at the top of the list.
The scroll bar and find function can be mitigated, but not as elegantly.
The real problem is that, when you load a page in the middle, it’s easy to scroll down, but scrolling UP is glitchy. That one can’t be fixed. https://meta.discourse.org/t/scroll-jank-when-scrolling-up/1...
If I had my way though... never!