canvas 2d context
Encrypted Media Extensions
HTML 5 spec
HTML 5: The Markup Language
HTML WG website
HTML5 differences from HTML4
HTML5 Spec - PR Blockers
Media Source Extensions
pre-LC1 alt techniques
pre-LC1 authoring guide
pre-LC1 HTML 5 spec
Erika Doyle Navara
Philippe Le Hégaret
Joshue O Connor
Evidently, the meter element came about primarily so that people don't use the
Progress element incorrectly. This seems a poor reason to create a new
element. Either the Progress element needs to have a better definition in the
spec, to prevent incorrect use, or the progress element is so confusing or is
so capable of being misunderstood, it should be pulled from the spec,
Regardless of what happens with Progress, there seems little use case,
interest, or need for the meter element.
The meter element is supposedly acting as some form of static gauge, but
there's no way to associate exactly what it is that's being gauged, with the
gauge value. There is no way to specifically tie the value contained in the
meter element with the object, in such a way that the information can be useful
for web bots or other user agents. In addition, it's not particularly useful
for accessibility reasons, when text within a span element would be just as
useful, and just as viable.
As for a graphical display, it's just as simple to provide an image, or use
CSS, SVG, or Canvas, with the associated fall back defined for each.
Regardless, there is little instruction about how the element is displayed,
which adds to the general confusion about what the element is, and how it
should be supported.
Even the graphical example about half way through the section, showing Usenet
subscriptions, doesn't really add much information. One can see that 618
subscribers is significantly more than 22, just by reading the numbers--one
doesn't to see a picture to comprehend the difference. On the contrary, without
understanding why there seems to be an upper range, the gauge doesn't mean a
lot. Is the upper range a Usenet limit? The largest Usenet membership? Some
arbitrary number picked so one can have a cool picture?
In addition, the section mixes instructions for authors and user agents, HTML
editing and parsing in a confusing mish-mash of instructions, compounded by a
list of confusing rules about the interaction of the element's attributes and
values. One can almost guarantee that this element will be used incorrectly,
and most likely implemented incorrectly.
Add notes (no markup allowed, URIs get automatically hyperlinked):
Resolved by WG decision.