-
Notifications
You must be signed in to change notification settings - Fork 395
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
Use HTML 5 widgets #594
Milestone
Comments
jelly
added a commit
to jelly/arch-security-tracker
that referenced
this issue
Mar 15, 2022
Widgets are now HTML5 by default wtforms/wtforms#594 and wtforms/wtforms#614
jelly
added a commit
to jelly/arch-security-tracker
that referenced
this issue
Mar 15, 2022
Widgets are now HTML5 by default wtforms/wtforms#594 and wtforms/wtforms#614
anthraxx
pushed a commit
to archlinux/arch-security-tracker
that referenced
this issue
Mar 17, 2022
Widgets are now HTML5 by default wtforms/wtforms#594 and wtforms/wtforms#614
anthraxx
pushed a commit
to archlinux/arch-security-tracker
that referenced
this issue
Mar 17, 2022
Widgets are now HTML5 by default wtforms/wtforms#594 and wtforms/wtforms#614
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The HTML 5 widgets are kept in their own section and not used by default, but this distinction doesn't make sense today. "HTML 5" is just "HTML" now. No supported browser doesn't understand those input types, and ones that aren't supported fall back to text anyway.
I already sort of started this by making the required validators add the
required
flag, and I'm taking it further with #406 for more complex flags. Fields should default to using the more specific widgets where possible.The text was updated successfully, but these errors were encountered: