Validation error on Mobile Safari
See original GitHub issueSetting enableTime: true
prevents form submit on Safari on iPhone. Instead the error message “Enter a Valid Value” is shown.
Demo: https://jsfiddle.net/jwm7c60q/
Result:
I tried mitigating the bug by setting novalidate
in the onReady
handler but was not successful.
- flatpickr version used: 4.6.9
- Browser name and version: Mobile Safari 13.1.2
- OS and version: iOS 13.6.1
- System: iPhone 8
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (2 by maintainers)
Top Results From Across the Web
I am getting validation error mess… | Apple Developer Forums
I am having trouble creating a sandbox tester account in App Store. I keep getting an error message saying there are one or...
Read more >iOS Safari/Chrome won't scroll up to show validation error ...
When the form is submitted/validated, and a question is not answered, it scrolls to the first invalid field - whether it is a...
Read more >On iOS Safari/Chrome won't scroll up to show validation error ...
On iOS Safari/Chrome won't scroll up to show validation error message on radio input. Active. Project: Webform. Version: 7.x-4.24.
Read more >Validation Error in Safari - Knowledge Link
Validation Error in Safari · 1. Open the Safari menu and select Preferences: · 2. Select Privacy settings and modify them:.
Read more >Solution: Make HTML5 Validation Work in Safari (iOS & OSX)
Solution: Make HTML5 Validation Work in Safari (iOS & OSX) · You need to modify this example code with your values before it...
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 Free
Top 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
Hey @bgold0, I’ve been quite busy with work. Gonna take a look in the next few days, no need to sponsor anything it’s likely an easy fix
I just tested this again on iOS 16.0 and again can not reproduce the issue anymore. I’d say this has been resolved somehow.