Random erasing of search query on Chrome 92 Android
See original GitHub issueDescription
When running on Android Chrome 92, I get weird behavior. When I enter a search string, everything works fine until I hit a certain letter. Then everything in the search field is removed.
It varies which letter causes the glitch. Check out the video below for an example:
https://www.youtube.com/watch?v=rYf5dsW5KKQ
I am using the following versions:
"@algolia/autocomplete-js": "^1.3.0",
"@algolia/autocomplete-plugin-algolia-insights": "^1.3.0",
"@algolia/autocomplete-plugin-query-suggestions": "^1.3.0",
"@algolia/autocomplete-plugin-recent-searches": "^1.3.0",
"@algolia/autocomplete-theme-classic": "^1.3.0",
"algoliasearch": "^4.10.5",
"algoliasearch-helper": "^3.5.5",
"htm": "^3.1.0",
"instantsearch.css": "^7.4.5",
"instantsearch.js": "^4.28.0",
Example (as shown in the video): I enter “se” in the search field. As soon as I enter “k”, “se” is removed and “k” is the only thing appearing in the search field.
When I inspect the state-object with the onStateChange event of Autocomplete, I find the the prevState does contain the first letters while the current state only contains the new letter.
I am actually seeing the same behavior in this official autocomplete-js example: https://l7tzs.csb.app/ (which is linked from the “See live demo” button on the page https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/autocomplete/js/
Here is a video where I demonstrate the bug on this specific sandbox example: https://youtu.be/rSbl26XJ828
Also asked about this on the community forum: https://discourse.algolia.com/t/possible-bug-on-chrome-android-erases-everything-in-input/13346
Environment
- OS: Android
- Browser: Chrome 92
- Autocomplete version: 1.3.0
Issue Analytics
- State:
- Created 2 years ago
- Comments:28 (10 by maintainers)
Thanks. It works.
I thought the world of quirk was gone with IE11, but it seems the spirit lives on, just manifesting in new ways. Perhaps the rendering engine of Android Chrome is in fact IE11?
Anyway. Looking forward to testing this out. It has been a quirky thing to figure out, and I admire the work that must have been put into locating and fixing the bug.