3 ms·
I'm enthused, but would suggest you don't put an entry in the user's history for every keystroke in the search box.
by fleshweasel 11y ago
I'm enthused, but would suggest you don't put an entry in the user's history for every keystroke in the search box.
- fphilipe 11y agoYes, this! People seem not to know when to use replaceState over pushState. And in my eyes this is a clear candidate for replaceState. (There are also examples the other way around, such as GitHub's PR tabs, drives me insane every time.)
- joemcelroy 11y agoYes! Thanks for noticing a side effect of the way we update our url. It should be replaceState for the search box. Other actions like pagination, applying filters and sorting should be pushState however. We also throttle the searchbox search requests as you type.
- ssetem 11y agothanks, will fix this today :D
- ssetem 11y agofixed now :), try the demo now http://searchkit.co http://searchkit.co