Cake
  • Log In
  • Sign Up
    • say... not sure if it is just my browser, or something weird, but..

      ...when I look at a longer conversation and I open the browsers search-on-page function, I can only find things that are visible in the window right now. Anything that is only reachable by scrolling - not there, according to the search function.

      Is that just me, or a general thing?

    • Hi JollyOrc,

      We handle long conversations by loading only the part in the vicinity of where you're reading in order to make the page load as fast as we can and lighten the burden on your device.

      The downside is the in-browser search function doesn't have the whole conversation available to search. There doesn't seem to be a way to have both. We do have sitewide search within the Explore tab, does that help? I wish we had a better answer for you.

    • the sitewide search doesn't really help. Let me explain the usecase: I see a long discussion, coming late to the party. I read it, and sometime near the end someone refers to something further up. So I hit "ctrl-f" and enter the word being referred, to find the comment being referred to. Except I can't, because the search only looks at the current screen.

      The site-wide search won't help either, because it would necessitate reloading the whole page, and all context is lost again. The extra nasty-part is that the local search is mostly needed when there is lots of text on the page, so it's a bit of catch-22: I don't need the search if the discussion is short enough that it has fast load time.

      In the end, I can only strongly urge you to refactor the code displaying the page, make it load fast even with large amounts of text. (maybe keep pictures etc. unloaded until visible?) I mean, it's just text, how big can that be?

    • Hey @JollyOrc, thanks for letting us know this is important to you!

      So I hit "ctrl-f" and enter the word being referred, to find the comment being referred to. Except I can't, because the search only looks at the current screen.

      This really bugs me too, so I'd like to find a good solution that doesn't require us to always load lots of posts the user doesn't intend to read. As @Chris said though, it's tricky. Browsers don't currently give developers any control over the in-page search functionality, so if we want to make something searchable on the page, we have to actually render it on the page.

      In the end, I can only strongly urge you to refactor the code displaying the page, make it load fast even with large amounts of text. (maybe keep pictures etc. unloaded until visible?) I mean, it's just text, how big can that be?

      We actually already do wait to load most images until they're visible.

      Even with just text, this is a difficult performance problem. For a fast computer on a fast connection, loading and rendering 25 or 50 or even 100 posts isn't too big a deal. But for a slow device like a phone, which may have a spotty connection, it could be a long wait and it would be a real battery killer.

      When someone clicks a link to the last post in a conversation with hundreds of posts, like this one, we want it to load as quickly as possible so they don't get frustrated or lose interest. So we've made a tradeoff that improves performance, at the expense of making in-page search functionality less useful.

      The good news is that there's actually already a discussion underway between web developers and browser makers about adding browser functionality that would make in-page searching possible in scenarios like this one. And there may be other things we can try in the meantime. We'll see what we can come up with.

    • maybe load things at least in larger chunks and have a "load more" button or pagination? I frankly find a browser search much more useful than continuous scrolling, especially if that scrolling doesn't give me the one thing that "everything on the same page" should deliver - ie local search.

    • Markos Giannopoulos

      I suppose lazy-loading the rest of thread while you read the first posts would have the UX effect?

      I had the same problem earlier, looking for something specific in a thread but not finding anything although there was a mention of the word I was searching for :)

    You've been invited!