Re: [csswg-drafts] [css-ui] appearance: base to enable interoperable styling of controls/components (#5998)

@fantasai 
> The reasons given for handling this as an attribute rather than in CSS (even though it is about presentation and otherwise would belong in CSS):
> 
> * DOM modifications that depend on CSS computed values are messy/difficult to implement

That is a separate pain point that should be addressed for authors as well. 

> * We need to be able to style differently depending on whether the element is basic or not, and an attribute allows for selecting against that.

In what way?

> * An attribute is less likely to create the forwards-compatibility problem that rules like `* { appearance: base }` would create if only some form elements supported basic rendering and others didn't.

Assuming that form controls are actually still functional with `appearance: base`, this doesn’t actually seem like the end of the world? Compact impact (not just the quantity, but also the type of impact) is a factor to consider when making changes, weighed against the benefit of the change. It doesn’t mean that if there is *any* compat impact, the change should not be made. In this case, form control rendering without `appearance: base` is "anything goes" anyway, so I don't see how a base appearance is any different than a different default style for these use cases.

-- 
GitHub Notification of comment by LeaVerou
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5998#issuecomment-2100910697 using your GitHub account


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

Received on Wednesday, 8 May 2024 16:02:02 UTC