Re: [csswg-drafts] [css-ui-4] Define how to compute the kind of widget to use for an element (#6537)

In https://bugzilla.mozilla.org/show_bug.cgi?id=1730147#c5 @emilio wrote

>> For meter, Chromium has the same rendering between the two, while WebKit and Gecko have different rendering. But for progress all browsers seem to agree to have different appearances (the second being like appearance: none).
>
> I think ~all browsers agree on disabling native styling when backgrounds/borders are specified on ~all html-exposed widgets except checkboxes and radios. So I'm not sure why meter would be different, so I think Gecko/WebKit behavior is slightly better.

When I worked on this originally, browsers were less consistent, and the `appearance: none` rendering for `progress` and `meter` in some browsers was *no* style and render the children (like a `span`). There were objections to that behavior, and it has now changed in browsers. But it seems the new normal is to do the *fallback* thing for `progress` and `meter`. See https://github.com/w3c/csswg-drafts/issues/356

-- 
GitHub Notification of comment by zcorpan
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/6537#issuecomment-931716364 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 30 September 2021 21:25:58 UTC