P-Chips component enter function not working in any Android devices

[leoademi]

Describe the bug

Im using the p-chips component from PrimeNG. In the mobile ( Android only ) the enter function does not create the chip in Android , but in IOS works fine. In Android it behaves the enter like the next tab ( next input )

Environment

Android devices only

Reproducer

No response

Angular version

Angular 16

PrimeNG version

"primeflex": "3.3.1", "primeicons": "6.0.1", "primeng": "16.0.2",

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

18

Browser(s)

Android Devices

Steps to reproduce the behavior

No response

Expected behavior

No response

[SoyDiego]

Hi @leoademi, I tried in Android and I cannot reproduce the problem.
It's working perfectly in my device.

[GustavoCostaW]

Same here, @SoyDiego I'm using pixel 7, it only happens on Android, even using commas or pressing enter does not work on any demo, testing the same page on chrome desktop works fine.

[SoyDiego]

Same here, @SoyDiego I'm using pixel 7, it only happens on Android, even using commas or pressing enter does not work on any demo, testing the same page on chrome desktop works fine.

Thanks for report it. I have checked with my mobile again (when I left my previous comment was 3 months ago) and now yes, I can replicate and see the problem in mobile. PRs are welcome too.
I'm only a contributor here, i'm not working for PrimeNG :)

[SoyDiego]

I was trying to fix the problem, but after a lot of investigation and trying many things, I don't know what else I can do. Maybe someone has another idea. I found that there was a big discussion about this issue on Android created and closed in the Chromium bugs. They closed it as WontFix.

Also I found this reply in StackOverflow:

So, will be complicated. I write here all the information because maybe @cetincakiroglu you have some another idea to continue with this issue, but it's not PrimeNG, it's Android problem :(

[Lukasss93]

See this:
primefaces/primevue#3694 (comment)

[mehmetcetin01140]

Hi,

So sorry for the delayed response! Improvements have been made to many components recently, both in terms of performance and enhancement. Therefore, this improvement may have been developed in another issue ticket without realizing it. You can check this in the documentation. If there is no improvement on this, can you open a new issue so we can include it in our roadmap?

Thanks a lot for your understanding!
Best Regards,