You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Getting this client-side warning, hundreds of times:
"A form field element has neither an id nor a name attribute. This might prevent the browser from correctly autofilling the form.
To fix this issue, add a unique id or name attribute to a form field. This is not strictly needed, but still recommended even if you have an autocomplete attribute on the same element."
🔍 Steps to reproduce
React InstantSearch... tried adding an "id" and "name"" attribute to SearchBox, for example, but it does not pass it as an HTML attribute to the "input" node.
Live reproduction
none
💭 Expected behavior
Both id and name attributes should be passed from the SearchBox and RefinementList elements to the actually rendered node. Or, add some automatically.
Package version
react-instantsearch latest
Operating system
macOS 14.6.1
Browser
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
🐛 Current behavior
Getting this client-side warning, hundreds of times:
"A form field element has neither an id nor a name attribute. This might prevent the browser from correctly autofilling the form.
To fix this issue, add a unique id or name attribute to a form field. This is not strictly needed, but still recommended even if you have an autocomplete attribute on the same element."
🔍 Steps to reproduce
React InstantSearch... tried adding an "id" and "name"" attribute to SearchBox, for example, but it does not pass it as an HTML attribute to the "input" node.
Live reproduction
none
💭 Expected behavior
Both id and name attributes should be passed from the SearchBox and RefinementList elements to the actually rendered node. Or, add some automatically.
Package version
react-instantsearch latest
Operating system
macOS 14.6.1
Browser
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: