With formatInput: false, Javascript validation is done incorrectly
See original GitHub issueWhen using the formatInput: false
option with hosted fields, Braintree doesn’t validate inputs correctly: entering “4111-1111-1111-1111”, for example, generates an unusable nonce with card type “Unknown”.
Example: http://codepen.io/anon/pen/rWKoMQ
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:8 (6 by maintainers)
Top Results From Across the Web
Validation returning false when correct condition is met - ...
Im learning Javascript and am trying to set up a basic form validation which should have the following functionality: If error is found...
Read more >Client-side form validation - Learn web development | MDN
Client-side form validation sometimes requires JavaScript if you want to ... in the wrong format, is incorrect, or is omitted altogether.
Read more >Import format quotas and validation - Amazon DynamoDB
Common causes for data validation errors include objects being unparsable, objects being in the incorrect format (input specifies DYNAMODB_JSON but the ...
Read more >Moment.js | Docs
Note: In case of multiple wrong units the first one is returned (because days validity may depend on month, for example). Invalid Moments....
Read more >Input Pattern: Use It To Add Basic Data Validation In ...
The pattern attribute of the <input> element allows you to add basic data validation without resorting to JavaScript. It works by matching the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Looks like this regression happened way back in 3.8.0. Looks like a PR that was in progress didn’t handle the merge conflicts correctly. We’ll get this fixed.
This has been fixed in 3.33.0