Browser: Chrome 110
OS: macOS
URL: Screenshot & Forum Post
I’m still trying to resolve my issue with Infinite Scroll and have been digging through the JavaScript source to find a way to pause and resume loading.
While investigating, I came across the Offset setting, but I don’t understand its purpose. Looking through the Bricks source code, I couldn’t find any references indicating that this setting is actually used by the Infinite Scroll feature.
Could you clarify what the Offset setting is intended to do and whether it is currently implemented for Infinite Scroll? If it is being used, it would be helpful to know where and how it affects the loading behavior.
Hi Ben,
The infinite scroll offset controls how early Bricks loads the next batch of posts before the visitor reaches the end of the current results.
For example, if the offset is 300, the next page of items starts loading when the visitor is about 300px before the bottom/load trigger. A larger offset loads earlier, which can feel smoother on slower connections. A smaller offset waits longer, which can reduce unnecessary requests.
In short, it is a preloading distance for infinite scroll, which works as expected as far as I can see. I’ll mark this report as a NO BUG for now.
Regarding the linked forum thread: The “best” way I can imagine is to use a load more interaction (on click) instead of the infinite scroll, so the user can decide if they want to load more posts, or keep on scrolling.
1 Like
Thank you for taking the time to explain this.
1 Like