81–90 of 97 posts
Infinite scroll is one of those things that needs to die.
Not saying there aren't bad implementations of infinite scroll out there, those do need to die off, but they aren't that common.
facebook, twitter etc have decided that their content is so low quality it's not even worth searching so they re just not supporting it
I see lots of replies suggesting scrolling for a long time and then using CTRL+F. However, this won't work if the page is using virtualised scrolling (common with React et al. SPA for performance reasons, to avoid huge DOM trees as the page expands). The majority of content that is outside of the visible window will simply be unmounted from the DOM. I'm not sure what the best-practice for a webapp designer is here? P…
> Perhaps intercepting Ctrl+F Please don't ever do that. I know one site that does this and I hate it.
I cannot think of one single use case where infinite scroll makes sense compared to plain old data tables that are paginated with server side search/pagination built in.
You can paste something like this into your javascript console: setInterval(function() { window.scrollTo(0, document.body.scrollHeight); }, 2000); That will scroll continuously, so you can let it run for a while and then do ctrl-F. It might take a while but you can do something else. I've used it successfully many times (usually when I wanted to scrape the DOM for some reason or another, rather than just do a search)…
Earlier quoted context omitted.
Discourse [1], popular forum software, does this as well. [1] https://www.discourse.org/
This is infuriating. Every time I CTRL+F on Discourse I get upset.
Fix: Just add a dummy onkeyup function to the document root and body elements, and set @match rules for whatever sites annoy you. Occasionally you'll also need the more generic event handler function as well.
Earlier quoted context omitted.
I agree with this. I feel like infinite scroll gets a bad rap. Pagination is no better. There are some sites and use cases where infinite scroll is a huge usability improvement. (I know -- pagination gives you a URL to a specific page of results. Who cares? When was the last time you deep-linked into a specific index page? Doing so is probably a bad idea, since when new content gets added, the contents of a specific…
> Doing so is probably a bad idea, since when new content gets added, the contents of a specific index pagination will change unless you paginate in chronological order rather than reverse chronological. but no one does.
Earlier quoted context omitted.
> Perhaps intercepting Ctrl+F Please don't ever do that. I know one site that does this and I hate it.
Google Docs does this, e.g. in a spreadsheet. I think it's reasonable in that context. For what it's worth, if you really need to search e.g. "View" to figure out where the View menu is, the OS-native menu option still works.