Closed prasanna1211 closed 4 years ago
Adding a set of issues here.
First one being, I think list box shouldn't have close button.
For pointer hover, cursor should be pointer for close button right ?
Adding a set of issues here.
First one being, I think list box shouldn't have close button.
As per the standard there is no close button for combo-box, it's part of UX I guess. May we can make it hide with props if they don't want or by default it will be hidden and can have it with props
When the value is not a valid option's value, the component shouldn't break. Instead no option should be selected.
Not a bug: A little confusion in behaviour of listbox. When we type then, choose the dropdown closes. If we type when it is still focused, the value changes. This happens in native select box too. But never seen it in the accessibility docs.
In async while we type, pressing enter clears the text. Intended ?
There are a few open source standards that we generally do, even at times when certain things are obvious to avoid breaking the code. These are done generally when typescript is not used.
Type check once, for every function by typeof x == 'function'
. Example, this shouldn't be an error. Instead a default filter function should load.
Same way for all functions. I could see this being there in the source at few places. Should extend it everywhere.
I think Pressing space bar when the input is empty needs a different behaviour. Currently it treats as a space which generally not used to be the case. react select, selects the first option when the dropdown is open and the space bar is pressed.
Closing this in favour of now individual issues being created.
As per #52 , needs following features
General behaviours
Backspace
sometimes clears the input directly without deleting a single letter.(hard to reproduce but happens then and there)Async component
Multiple Select
Custom Option
Rewrite Composition