Some article websites (I’m looking at msn.com right now, as an example) show the first page or so of article content and then have a “Continue Reading” button, which you must click to see the rest of the article. This seems so ridiculous, from a UX perspective–I know how to scroll down to continue reading, so why hide the text and make me click a button, then have me scroll? Why has this become a fairly common practice?

  • You can, but you would have to do it through scripting which would rely on whatever methodology you’re using not breaking with browser updates and standards changes, whether or not the user has scripting enabled to begin with, whether not their adblockers or other plugins mess it up, etc. And then you can wind up just deferring the issue. Let’s say the user intends to quickly skim through your page to see if it actually appears to contain what they’re looking for or whether it’s just SEO bullshit, so they scroll down right after the first chunk loads and hit the point where the next chunk should load, and unexpectedly find that it didn’t do so instantly (because it probably won’t) and it appears your content cut off mid-page. They’ll assume your site is just broken and you’ve never seen another user hit that back button so fast.

    So the answer is “yes, but,” and may not be worth the trouble.

    Clicking a “continue reading” button is not an ideal solution either, but at least the user will (should) realize that they’ve performed an action that will load more content, as opposed to having it happen behind their backs in a manner that they weren’t initially aware.

    • Anamnesis@lemmy.world
      link
      fedilink
      arrow-up
      4
      ·
      1 year ago

      Yeah this shit annoys the hell out of me with certain websites where I’m trying to ctrl-f information. It hasn’t loaded the whole page until I scroll down, so my search ends up being worthless.