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 Report] <v-text-field> with type="number" allows non-numeric characters in Edge #9314

Closed
1kevgriff opened this issue Oct 10, 2019 · 3 comments
Labels
upstream Problem with a third party library that we may have to work around wontfix The issue is expected and will not be fixed

Comments

@1kevgriff
Copy link

Environment

Vuetify Version: 2.1.2
Vue Version: 2.6.10
Browsers: Microsoft Edge
OS: Windows 10

Steps to reproduce

  1. Go to CodePen
  2. Type in number, and the number model should update
  3. Type in "1,234" and the number model will go blank or ""

Expected Behavior

should not allow the input of non-numeric characters if the type="number"

Actual Behavior

Backing model of the text field holds an empty string

Reproduction Link

https://codepen.io/1kevgriff/pen/bGGVWBP

Other comments

I understand this is because of Edge not having proper support for type="number", but was expecting Vuetify to overcome some of the limitations of browser support.

@ghost ghost added the S: triage label Oct 10, 2019
@1kevgriff
Copy link
Author

Also, not an issue on Edge Insider Builds that use Chromium.

@1kevgriff
Copy link
Author

1kevgriff commented Oct 10, 2019

Workaround: I had to capture the @keypress event and manually reject the input if it was not a number.

@KaelWD KaelWD added upstream Problem with a third party library that we may have to work around wontfix The issue is expected and will not be fixed and removed S: triage labels Oct 11, 2019
@KaelWD
Copy link
Member

KaelWD commented Oct 11, 2019

This is the same behaviour as <input type="number">, we don't handle it any differently.

See also #3118, #7374

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
upstream Problem with a third party library that we may have to work around wontfix The issue is expected and will not be fixed
Projects
None yet
Development

No branches or pull requests

2 participants