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
When search on the Select component is set to false, it appears that the user cannot type into the input field, but the value is still being captured.
Expected behavior
No value should be captured when search is set to false.
A potential solution is adding readOnly: !state.search to the inputProps in packages/select/src/select-input.js.
This was made workable by adding the readOnly prop to the select input, since it will pass that prop along to the Input component, along with search={false}.
Any message or error
N/A
Resources
N/A
The text was updated successfully, but these errors were encountered:
Prerequisites
@rent_avail/select@0.3.10
Step to reproduce (actual behavior)
When
search
on theSelect
component is set tofalse
, it appears that the user cannot type into the input field, but the value is still being captured.Expected behavior
No value should be captured when
search
is set tofalse
.A potential solution is adding
readOnly: !state.search
to theinputProps
inpackages/select/src/select-input.js
.This was made workable by adding the
readOnly
prop to the select input, since it will pass that prop along to theInput
component, along withsearch={false}
.Any message or error
N/A
Resources
N/A
The text was updated successfully, but these errors were encountered: