Skip to content
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

Closed
faelgabriel opened this issue Jan 4, 2017 · 6 comments
Closed

Is there any specific reason to disallow HTML <progress> Tag? #6870

faelgabriel opened this issue Jan 4, 2017 · 6 comments
Assignees

Comments

@faelgabriel
Copy link

faelgabriel commented Jan 4, 2017

Is there any specific reason to disallow HTML <progress> Tag?
It's a HTML5 element, is there an issue to allow this tag?

@jridgewell
Copy link
Contributor

/to @Gregable

@Gregable
Copy link
Member

Gregable commented Jan 4, 2017

I don't see any reason why not. I'm unsure why it was missed. I'll add it.

@Gregable
Copy link
Member

Gregable commented Jan 4, 2017

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 <meter> and <output> while at it.

@jridgewell
Copy link
Contributor

@Gregable: Remember to ban <output>s with special name properties.

@Gregable
Copy link
Member

Gregable commented Jan 4, 2017

Yep, @honeybadgerdontcare reminded me of this one as I was implementing. Change is simple, but it'll be a while before released.

@rudygalfi rudygalfi added this to the Pending Triage milestone Jan 12, 2017
@honeybadgerdontcare
Copy link
Contributor

This is now live in prod.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants