Skip to content

Issue315 - let data-validation-optional work on input type=number #379

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

Merged
merged 2 commits into from
Feb 5, 2016

Conversation

ray-print
Copy link
Contributor

No description provided.

* Add tests for input type=number
* Change spacing for better legibility
* Remove statement in core-validators which always evaluated to true
* Remove unnecessary if-else branch checking for data-validation-optional

If a value is entered into an input type=number that the browser cannot parse, the browser
sets the value of it to an empty string. This means that we can't tell the difference between
a browser-unparsable input and an empty input.
@victorjonsson
Copy link
Owner

Great! The input, of type number, is a tricky one...

victorjonsson added a commit that referenced this pull request Feb 5, 2016
Issue315 - let data-validation-optional work on input type=number
@victorjonsson victorjonsson merged commit d0a857e into victorjonsson:master Feb 5, 2016
@ray-print ray-print deleted the issue315 branch February 5, 2016 08:39
@ray-print
Copy link
Contributor Author

Cool.
Any other issues I can help with?

@victorjonsson
Copy link
Owner

Take your pick. I'm currently not working on any of them.

I'm available for discussion if there's something you feel we need to elaborate on, just post a message in the issue you'll be working with.

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

Successfully merging this pull request may close these issues.

2 participants