Open domenic opened 3 months ago
In Firefox I cannot find evidence of this being in the UA stylesheet, but instead these properties seem to show up as applied to
in some other way.
Firefox seems to define some of these (like the vertical-align
and the fallback gradients) in forms.css
The suggested changes make sense to me and seems in line with what CSS UI expects.
Last I checked there was no standardized pseudo-element for meter
. That seems necessary to specify the primitive appearance (and allow authors to change the style without relying on vendor-prefixed pseudos).
cc @nt1m @pxlcoder @whatwg/css
What is the issue with the HTML Standard?
This issue is the HTML-side counterpart of https://github.com/w3c/csswg-drafts/issues/356.
After https://groups.google.com/a/chromium.org/g/blink-dev/c/UquTxWTNON0, all browsers seem to have specified an appearance for
<meter>
whenappearance: none
is specified on it. That appearance seems to be some combination of:plus some stuff that is not in the UA stylesheet to style the inner parts of the meter in specific colors as linear gradients. (Which, at least eyeballing them, seem to be the same colors across all browsers.)
In Firefox I cannot find evidence of this being in the UA stylesheet, but instead these properties seem to show up as applied to
<meter>
in some other way.The HTML spec currently says:
which covers some of the above but not all. Note the "native appearance": this supposedly only applies for the
appearance: auto
case, not theappearance: none
case. And it uses "expected to render" wording, seems closer to Firefox's behavior than to Safari/Chrome; the latter use the actual UA stylesheet.I think an appropriate set of changes here would be:
I'm unsure if this fits the exact intent of how the CSS UI spec intends to integrate with HTML, but I think it's right.
/cc @tcaptan-cr @zcorpan @dizhang168 @frivoal @tabatkins