- From: Mats Palmgren via GitHub <sysbot+gh@w3.org>
- Date: Fri, 15 May 2020 12:49:13 +0000
- To: public-css-archive@w3.org
> I like what Chrome does for `meter` and think should be [adopted for `progress`](https://bugs.chromium.org/p/chromium/issues/detail?id=609687) as well. It lets authors show fallback content if they so wish, and gives them flexibility to create an entirely custom widget I disagree that this is a desirable behavior. It goes against how HTML normally defines when fallback content should be rendered - namely that it is intended as a fallback for UAs that don't support the element at all. As the current [spec says](https://html.spec.whatwg.org/multipage/form-elements.html#the-meter-element) for `<meter>`: > Authors are encouraged to include a textual representation of the gauge's state in the element's contents, for users of user agents that do not support the meter element. `appearance:none` should only disable the native theme and let authors style it using CSS, that's all. Showing alternate content is an orthogonal issue. -- GitHub Notification of comment by MatsPalmgren Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/356#issuecomment-629217177 using your GitHub account
Received on Friday, 15 May 2020 12:49:15 UTC