Skip to content
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

[Bug]: NumberInput clicking the +/- buttons throw errors when using touch screen #784

Closed
erikarenhill opened this issue Oct 31, 2023 · 2 comments · Fixed by #785 or #789
Closed

[Bug]: NumberInput clicking the +/- buttons throw errors when using touch screen #784

erikarenhill opened this issue Oct 31, 2023 · 2 comments · Fixed by #785 or #789
Assignees
Labels
Type: Bug Confirmed bug, something is not working as intended

Comments

@erikarenhill
Copy link

Tremor Version

3.10.1

Link to minimal reproduction

https://codesandbox.io/p/sandbox/friendly-noether-wgq24q?file=%2Fcomponents%2FBugRepro.js

Steps to reproduce

Set browser in mobile device mode (in chrome open developer toolbar and click the small icon to the left to toggle for example responsive dimensions mode)
Click the + or - button on a NumberInput and watch the console

What is expected?

No error thrown

What is actually happening?

Error gets thrown: "Unable to preventDefault inside passive event listener invocation."
Stacktrace show it is in thrown at onTouchStart

What browsers are you seeing the problem on?

Chrome

Any additional comments?

This also happens on the official docs: https://www.tremor.so/docs/components/number-input

@severinlandolt severinlandolt linked a pull request Oct 31, 2023 that will close this issue
14 tasks
@severinlandolt severinlandolt added the Type: Bug Confirmed bug, something is not working as intended label Oct 31, 2023
@severinlandolt severinlandolt self-assigned this Oct 31, 2023
@github-actions
Copy link

🎉 This issue has been resolved in version 3.11.0-beta.8 🎉

The release is available on:

Your semantic-release bot 📦🚀

Copy link

github-actions bot commented Nov 6, 2023

🎉 This issue has been resolved in version 3.11.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Confirmed bug, something is not working as intended
Projects
None yet
2 participants