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

[RAC] NumberField really strange behavior #7015

Open
scythewyvern opened this issue Sep 9, 2024 · 3 comments
Open

[RAC] NumberField really strange behavior #7015

scythewyvern opened this issue Sep 9, 2024 · 3 comments

Comments

@scythewyvern
Copy link

scythewyvern commented Sep 9, 2024

Provide a general summary of the issue here

when entering ., after certain actions the previous number appears in the field but in a different locale

number-field-bug.mov

see Steps to Reproduce below

🤔 Expected Behavior?

input should not allow me to type ,. | ., or handle it correctly

😯 Current Behavior

input behaves strangely, replacing the value from one locale to another when typing ,. | .,

💁 Possible Solution

maybe some cache issues?

🔦 Context

No response

🖥️ Steps to Reproduce

You can reproduce it right on the official website

  1. follow to NumberField docs https://react-spectrum.adobe.com/react-aria/NumberField.html#example
  2. there is already some default value
  3. delete the default value
  4. type ,. and blur
  5. see that now there is the same value but in different locale
  6. delete the value
  7. type ,. again and blur
  8. see the same result
  9. delete the value
  10. type ., and blur
  11. see original value in original locale
  12. type some different value for example 808 and blur
  13. repeat the actions from 3 to 11
  14. you can see the same behavior but with different value

Version

1.3.3

What browsers are you seeing the problem on?

Chrome, Safari

If other, please specify.

No response

What operating system are you using?

macOS

🧢 Your Company/Team

No response

🕷 Tracking Issue

No response

@scythewyvern
Copy link
Author

#3862

this seems to be a known issue for a long time

@majornista
Copy link
Collaborator

This PR may also be relevant: #6520

@scythewyvern
Copy link
Author

This PR may also be relevant: #6520

I tried it on the latest build (on StoryBook) but this behavior still persists

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants