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
{{ message }}
This repository has been archived by the owner on Dec 23, 2022. It is now read-only.
I am using formik, and manually handling the chip array to submit items to the back end. However, I noticed that on mobile when hitting enter it goes to the next field as opposed to adding another chip.
Not sure if this is a formik issue or mui-chip-issue. I know I can change the newChipKeys, should I change it to 'space'?
Any help or direction would be greatly appreciated
tested on Android
The text was updated successfully, but these errors were encountered:
brandonhdz
changed the title
On Mobile 'enter' Chip is not Working With Formik
On Android Mobile: newChipKeys not working
Feb 19, 2021
brandonhdz
changed the title
On Android Mobile: newChipKeys not working
On Android Mobile: newChipKeys not working
Feb 19, 2021
UPDATE: I tried using newChipKeyCode={[32, 62]} even with that it wasn't working. It seems as though this might be an issue with android and also deprecated.
Because of this I started using newChipKeys={['Space', ' ', /\/a/]} Even so they are still not being registered on Android(Samsung Note 10). Even when I test it here the key is Unidentified, but it does register a space: " ". Is there a better way to check for this in newChipKeys?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am using formik, and manually handling the chip array to submit items to the back end. However, I noticed that on mobile when hitting enter it goes to the next field as opposed to adding another chip.
Not sure if this is a formik issue or mui-chip-issue. I know I can change the
newChipKeys
, should I change it to'space'
?Any help or direction would be greatly appreciated
tested on Android
The text was updated successfully, but these errors were encountered: