-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Is there any specific reason to disallow HTML <progress> Tag? #6870
Comments
/to @Gregable |
I don't see any reason why not. I'm unsure why it was missed. I'll add it. |
OK, now I see why it was originally left out. It's part of section 4.10 (forms) of the HTML5 spec. Forms weren't originally supported in AMP and so form related elements were also left out. There is no reason not to add them in at this point. I'll also add |
@Gregable: Remember to ban |
Yep, @honeybadgerdontcare reminded me of this one as I was implementing. Change is simple, but it'll be a while before released. |
This is now live in prod. |
Is there any specific reason to disallow HTML
<progress>
Tag?It's a HTML5 element, is there an issue to allow this tag?
The text was updated successfully, but these errors were encountered: