Polling breaks the browsers auto-completion

[saeedvaziry]

@inertiajs/react Version

2.0.17

Backend stack (optional)

Laravel 12.x
PHP 8.4

Describe the problem

When setting polling like usePoll(5000) and completing a form in the same page, the auto-completion of the browser gets closed when it renders after a poll again.

Steps to reproduce

1. Set a usePoll(5000) in the page
2. Have a text input that has auto completion
3. Try to complete the input using browsers auto-completetion and wait for the next poll before you select any item

[eznix86]

I think usePoll re-renders the component tree. I think. instead of usePoll, just use visit with only instead of a global poll

[HichemTab-tech]

This isn’t related to React re-renders, a re-render alone shouldn’t mess with the browser’s auto-complete (Although i hate the fact that it has to rerender on every poll, I use React.memo with custom comparaison function all the time :"3 ). Anyway after some heavy digging , I found the issue actually comes from the use of window.history.replaceState, specifically here:

window.history.replaceState(
  {
    ...data,
    scrollRegions: data.scrollRegions ?? window.history.state?.scrollRegions,
    documentScrollPosition: data.documentScrollPosition ?? window.history.state?.documentScrollPosition,
  },
  '',
  url,
)

Not entirely sure why or how this affects auto-complete, but calling replaceState seems to interrupt it (There is something about autocomplete mentioned here but not this particular case specifically). I know it’s an important part of Inertia’s navigation flow, so changing it might not be easy.

Maybe if the page data hasn’t actually changed, we could skip the replaceState call, though I’m not sure that would help much (nor that it’s really worth the change). Or maybe in a future major version, Inertia could find another way to handle page data updates without relying so heavily on history state.

Anyway, just wanted to share what I found.