-
-
Notifications
You must be signed in to change notification settings - Fork 386
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DropDown header interaction inconsistent for input and TextInput vs other controls. #1341
Open
2 tasks done
Comments
dragonlipz
changed the title
DropDown header interaction inconsistent for input and TextInput control controls.
DropDown header interaction inconsistent for input and TextInput vs other controls.
Apr 5, 2024
Same is happening to me, thought the Dropdown may have an option to disable the navigation with first letters of the Items, but was not able to find any. |
Please any update on this, or any solution i can work with for now @polnetwork @dragonlipz |
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce
vite react-ts project
[email protected]
(was also occurring with previous versions of 0.7.x)App.tsx
contents withCode Example
at the end.onChange
handlerCurrent behavior
You will see the Key pressed value for
onKeyDown
andonKeyUp
but you will never see any output foronChange
. It appears theonChange
handler is being hijacked somewhere an not being called as a result.Non-AlphaNumeric keys seem to properly "act" in the field. (space, backspace, arrows move the cursor as expected)
Pasting a value into the field triggers
onChange
properly.Other
flowbite-react
controls such asTabs
,ToggleSwitch
,Checkbox
, etc., behave as expected.Attempting to type a the first character of one of the drop down values (in this case i) will jump you to a row starting with that character.
Expected behavior
input
andTextInput
controls would behave as normal. And I would be able to prevent the automatic search of items in the dropdown.Context
Code Example
The text was updated successfully, but these errors were encountered: