Skip to content
This repository has been archived by the owner on Dec 23, 2022. It is now read-only.

On Android Mobile: newChipKeys not working #344

Open
brandonhdz opened this issue Jan 27, 2021 · 1 comment
Open

On Android Mobile: newChipKeys not working #344

brandonhdz opened this issue Jan 27, 2021 · 1 comment

Comments

@brandonhdz
Copy link

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

@brandonhdz brandonhdz changed the title On Mobile 'enter' Chip is not Working With Formik On Android Mobile: newChipKeys not working Feb 19, 2021
@brandonhdz brandonhdz changed the title On Android Mobile: newChipKeys not working On Android Mobile: newChipKeys not working Feb 19, 2021
@brandonhdz
Copy link
Author

brandonhdz commented 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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant