It’s seems that the infiniteHits Load More button doesn’t expand hits container correctly since a google chrome update.
I use the last version of google chrome : Version 85.0.4183.102 (Official Build) (64 bits)
I have the same problem with edge but not in Firefox.
To explain what i mean, i made 2 videos (one with chrome and one with FIrefox) with the storybook example of infinite hits on algolia page.
I don’t know if it’s an algolia problem or a google problem.
Bad UX video (chrome) :
Good UX video (firefox) :
The problem is (with chrome) when user click on the button, he doesn’t see the first “new” hits but just the last ones. This is problematic because if you load 60 hits by page, users don’t understand where is the beginning of the new page and they are lost cause of the static results.
Until now the UX was the same as Firefox one and i want it back
On my professional website i use instant search v3 and there is the same problem… Maybe it’s a chrome/edge UX bug ?
Does some of you already saw the bug ? is there a fix ?