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.

Sign up for GitHub

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

Jump to bottom

.type() fails on input[type=number] fields in Chrome #90

Closed
michalbe opened this issue Dec 18, 2014 · 2 comments · Fixed by #184
Closed

.type() fails on input[type=number] fields in Chrome #90

michalbe opened this issue Dec 18, 2014 · 2 comments · Fixed by #184
Assignees
@ccummings
Labels
bug p2

Comments

@michalbe
Copy link
Contributor

Trying to type in a numeric input is throwing an error on Chrome:
screen shot 2014-12-18 at 12 50 49
JSFiddle example: here

It works fine in Fx for now, but according to WHATWG HTML Living Standard, selection is only permitted with text/search, URL, tel and password inputs, so we should expect this to fail in all the browsers in the near future.
@michalbe michalbe added the bug label Dec 18, 2014
@michalbe
Copy link
Contributor Author

Maybe we can temporarily change type of the input to text and change it back in teardown?

@zedd45
Copy link

zedd45 commented Mar 31, 2015

I'm having the same issue with type=emailand type=number on chrome 41.

@moschel can confirm this.

@m-mujica m-mujica mentioned this issue Mar 23, 2016
Closed
ccummings added a commit that referenced this issue Jan 24, 2017
@ccummings
Upgrade syn to 0.2.2 to fix #90
bbc397e
@ccummings ccummings mentioned this issue Jan 24, 2017
Merged
@ccummings ccummings self-assigned this Jan 24, 2017
justinbmeyer added a commit that referenced this issue Jan 25, 2017
@justinbmeyer
Merge pull request #184 from bitovi/upgrade-syn
cb06346 
Upgrade syn to 0.2.2 to fix #90 ~2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ccummings ccummings

Labels
bug p2
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Upgrade syn to 0.2.2 to fix #90 ~2 bitovi/funcunit
5 participants
@justinbmeyer @michalbe @ccummings @zedd45 @mickmcgrath13