[Autocomplete] clear tomselect instance to avoid double initialization

[daFish]

Q	A
Bug fix?	yes
New feature?	no
Deprecations?	no
Documentation?	no
Issues	Fix #2623
License	MIT

Problem

When Autocomplete elements are removed and re-added to the DOM (e.g., with Turbo navigation), a race condition causes
"Tom Select already initialized on this element" error.

Root Cause

disconnect() destroys TomSelect but leaves this.tomSelect pointing to the destroyed instance. If urlValueChanged()
fires before connect() (during re-attachment), it calls resetTomSelect() on the stale reference, triggering
double-initialization.

Impact

• Affects: Users with Turbo navigation, especially on mobile (Safari iOS)
• Symptoms: "Tom Select already initialized" console errors during navigation
• Fix: Single line addition prevents the race condition
• Risk: None - only affects the disconnect cleanup path

[github-actions]

📊 Packages dist files size difference

Thanks for the PR! Here is the difference in size of the packages dist files between the base branch and the PR.
Please review the changes and make sure they are expected.

File	Before (Size / Gzip)	After (Size / Gzip)
Autocomplete
controller.d.ts	1.95 kB / 656 B	1.96 kB+1% 📈 / 666 B+2% 📈
controller.js	15.02 kB / 3.88 kB	15.2 kB+1% 📈 / 3.91 kB+1% 📈

[daFish]

@Kocal I took the chance to add playwright tests. I'll submit another PR with some changes to the documentation to enhance the DX.

[Kocal]

Thanks Marcus, that's much appreciated!

I only have some comments about the E2E test, and of course any documentation improvement is welcomed :)

[daFish]

• removed the browser test because I couldn't find a way to reproduce it here
• added a simple non-ajax example for Autocomplete

[daFish]

Ok, this is weird. I have force-pushed my changes this morning and the PR is still not updated. My changes are still being processed. 🤨

[daFish]

Rebased against 2.x and force-pushed again. Works now.