Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Is there any specific reason to disallow HTML <progress> Tag?
See original GitHub issueIs there any specific reason to disallow HTML <progress> Tag?
It’s a HTML5 element, is there an issue to allow this tag?
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
The Progress Indicator element - HTML - MDN Web Docs
The HTML element displays an indicator showing the completion progress of a task, typically displayed as a progress bar.
Read more >Why not use <progress> for a gauge and not <meter> for ...
The HTML spec says the same thing: "The progress element is the wrong element to use for something that is just a gauge,...
Read more >The HTML5 progress Element | CSS-Tricks
A progress element must have both a start tag (i.e. <progress> ) and an end tag (i.e. </progress> ), even though it looks...
Read more >The progress element | HTML5 Doctor
The progress element represents the completion progress of a task. ... Since we have no idea how long the task in hand will...
Read more >HTML progress tag - Javatpoint
HTML <progress> tag is used to display the progress of a task. It provides an easy way for web developers to create progress...
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
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
<meter>and<output>while at it.