Hi Michael,
Thank you very much, this is exactly what I needed.
The response data is perfectly fine though, it contains all the information needed. I can replicate almost this same exact response (only the keywords are different, but the structure is the same), and the search stops immediately after the first try.
I conclude this is not a script issue then, it must be either CSS or something else.
I don’t quite recall, but is there any custom CSS in use affecting the ‘show more results’ container? I’m asking, because the script determines the loading via the show more container visibility, which is changed via the script, but it can be overwritten with a custom CSS rule.
In case you have any custom CSS rules, on the show more container, rules containing something like p.showmore or .showmore or p.showmore a, where the display property is changed, maybe something like:
display: block !important;
..or:
display: inline-block !important;
..or any other value on the display property within that rule, then this property must be removed for sure, as it will cause this problem. The other properties are fine, just this one forces the block to be visible all times, which is not okay.
I can’t think of any other possible explanation, I hope this is it.