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
I'd expect the id attribute to show up on the input element so that screen readers and other JS code can find it. In my case I'm trying to use the <Typeahead> with Formik's handleBlur handler so that Formik knows that the field has been touched, but since the ID isn't present on the relevant input Formik isn't able to tell which field has changed.
Actual Behavior
The id field doesn't show up at all on the <input> element. It appears that the aria-owns field does get populated with the ID that gets passed in.
The text was updated successfully, but these errors were encountered:
Hey. I'm not sure whether this is legitimately a bug, or if I'm misunderstanding how to use the
id
field.Version
^5.1.4
Steps to reproduce
The
id
attribute to<Typeahead>
appears not to be passed down the rendered<input>
. This can be reproduced with the basic exampleIt's also visible if you inspect element the examples on https://ericgio.github.io/react-bootstrap-typeahead/
Expected Behavior
I'd expect the
id
attribute to show up on theinput
element so that screen readers and other JS code can find it. In my case I'm trying to use the<Typeahead>
with Formik'shandleBlur
handler so that Formik knows that the field has been touched, but since the ID isn't present on the relevantinput
Formik isn't able to tell which field has changed.Actual Behavior
The
id
field doesn't show up at all on the<input>
element. It appears that thearia-owns
field does get populated with the ID that gets passed in.The text was updated successfully, but these errors were encountered: