Can't load the next 25 docs

[red-bin]

Hi there, not really doing anything fancy but a normal search, but when I scroll down to the bottom of the page it's unable to load the next 25 docs. Seems like this has been happening all day. For a moment it seems to actually work and momentarily displays "Showing 50 of 85 Results".. but then immediately switches back to "Showing 25 of 85 Results".

Here's the error in the console:

Uncaught (in promise) TypeError: IntersectionObserver.observe: Argument 1 is not an object. G ResultsList.svelte:151 F ResultsList.svelte:151 Ae ResultsList.svelte:151 Ae ResultsList.svelte:151 G ResultsList.svelte:151 qs ResultsList.svelte:151 y utils.js:41 Ft Component.js:47 ct scheduler.js:99 r await_block.js:55 Ee await_block.js:63 promise callbackEe await_block.js:60 p DocumentListToolbar.svelte:19 O utils.js:203 p Search.svelte:55 jt scheduler.js:119 ct scheduler.js:79 promise callbackat scheduler.js:20 It Component.js:81 ctx Component.js:139 jd Lodash u index.js:56 Lodash 7 ct scheduler.js:99 promise callback*at scheduler.js:20 ResultsList.svelte:151:60 Ae ResultsList.svelte:151 AsyncFunctionThrow self-hosted:804 (Async: async) forEach self-hosted:157 Ae ResultsList.svelte:151 (Async: IntersectionCallback) G ResultsList.svelte:151 qs ResultsList.svelte:151 y utils.js:41 map self-hosted:175 Ft Component.js:47 ct scheduler.js:99 r await_block.js:55 Ee await_block.js:63 (Async: promise callback) Ee await_block.js:60 p DocumentListToolbar.svelte:19 O utils.js:203 p Search.svelte:55 jt scheduler.js:119 ct scheduler.js:79 (Async: promise callback) at scheduler.js:20 It Component.js:81 ctx Component.js:139 jd Lodash u index.js:56 Nd Lodash InterpretGeneratorResume self-hosted:1332 AsyncFunctionNext self-hosted:800 Lodash 6 ct scheduler.js:99 (Async: promise callback) at scheduler.js:20

[duckduckgrayduck]

Could you tell us which web browser, OS, and what document set you're trying to view? I'm able to load the next 25 documents just fine on both Firefox and Chromium

[eyeseast]

Even if we can't reproduce the error here, we should make sure the UI gives you a useful error message and offers an alternative. There's already a button we can show to load more documents; we just need to show it.

We can probably catch this error (however it's happening) and disable auto loading.

[red-bin]

Thank you, I really appreciate that approach. At the end of the day I'm just trying to look at and share documents but I often feel like I'm spending as much time troubleshooting documentcloud weirdness. It's become extremely hard to disambiguate one problem from the next because they all have this "25 document" stink to them. So any UX workaround is genuinely appreciated.

Can't remember which documents I was looking at at the time but it was across more than one project throughout the day so I doubt it was project dependent. Was using firefox. It very much could've been a one-off thing from my browser being in a weird state.

[red-bin]

Had this issue again today! Shot Sanjin a message on Signal with the project name and search term that's giving me this problem.

Just a hunch, but the specific search I did resulted in quite a lot of text in the search results, where it takes a bit longer than normal to scroll down to the bottom.

[allanlasser]

We're no longer able to replicate this issue, so we're closing it. If we can point to a specific reproducible case, we can reopen.