Re: [csswg-drafts] [css-ui] Changing UA styles based on the computed value of the appearance property (#10028)

The CSS Working Group just discussed `[css-ui] Changing UA styles based on the computed value of the appearance property`, and agreed to the following:

* `RESOLVED: user agent styles can depend on appearance:base. Aim for eventual interoperability across all values of the property.`

<details><summary>The full IRC log of that discussion</summary>
&lt;emilio> jarhar: for appearance: base one of the things is that chrome and webkit have different border property and we want to make this interoperable<br>
&lt;emilio> ... for html-based solution this was not a proble<br>
&lt;emilio> problem*<br>
&lt;fantasai> s/popover or/<br>
&lt;fantasai> s/popover or//<br>
&lt;emilio> ... so I thought it'd be not possible to solve, but lilles suggested something like light-dark<br>
&lt;emilio> ... that took multiple values, one for auto/none and one for base<br>
&lt;emilio> ... I implemented it for border and so on<br>
&lt;RRSAgent> I have made the request to generate https://www.w3.org/2024/06/27-css-minutes.html fantasai<br>
&lt;emilio> ... not sure if you need details<br>
&lt;emilio> q+<br>
&lt;chrishtr> +1<br>
&lt;gregwhitworth> ack emilio<br>
&lt;fantasai> scribe+<br>
&lt;fantasai> emilio: This is fine, but I'm sad that we can't get interoperable UA stylesheets<br>
&lt;gregwhitworth> emilio: this seems fine, it makes me sad that we can't get interoperable UA stylesheets<br>
&lt;masonf> q+<br>
&lt;fantasai> emilio: The fact that now we cannot use regular CSS to represent the HTML styles is a bit unfortunate<br>
&lt;gregwhitworth> emilio: now we can not use regular CSS to represent the HTML styles is unfortunate<br>
&lt;gregwhitworth> emilio: either we define this entirely and we can use this from HTML then we have to say "if appearance is base" you need to do this<br>
&lt;jarhar> q?<br>
&lt;gregwhitworth> emilio: it makes me a bit sad that it would spec fiction but maybe it's fine<br>
&lt;tantek> +1 emilio, it is surprising that appearance:none is not interoperable across engines<br>
&lt;gregwhitworth> emilio: I think we should look into interoperable UA stylesheet. Appearance: none is not interoperable at this point<br>
&lt;gregwhitworth> ack masonf<br>
&lt;emilio> masonf: first I think this doesn't mean that we shouldn't work on making appearance: none interoperable, but decouples it<br>
&lt;emilio> ... so that we don't have to worry about that for now<br>
&lt;chrishtr> PROPOSED: user agent styles can depend on appearance:base<br>
&lt;jarhar> q+<br>
&lt;emilio> ... the other thing is that maybe there should be an author-visible way to do this<br>
&lt;gregwhitworth> ack jarhar<br>
&lt;emilio> jarhar: I agree we can work on make appearance: none more interop, but decoupling them is easier<br>
&lt;fantasai> i/Topic: [css-ui] DOM/scribe+ gregwhitworth/<br>
&lt;emilio> ... re author visibility, I had to implement it for each prop, so I'm reluctant to do that<br>
&lt;RRSAgent> I have made the request to generate https://www.w3.org/2024/06/27-css-minutes.html fantasai<br>
&lt;emilio> q+<br>
&lt;masonf> q+<br>
&lt;gregwhitworth> ack emilio<br>
&lt;gregwhitworth> zakim, close queue<br>
&lt;Zakim> ok, gregwhitworth, the speaker queue is closed<br>
&lt;gregwhitworth> emilio: can we resolve on the issue with the goal of making things interoperable and this function would go away<br>
&lt;gregwhitworth> emilio: once we make appearance: none consistent this would go away<br>
&lt;chrishtr> PROPOSED: user agent styles can depend on appearance:base. Aim for eventual interoperability across all values of the property.<br>
&lt;tantek> +1 emilio<br>
&lt;gregwhitworth> jarhar: sounds good to me<br>
&lt;gregwhitworth> ack masonf<br>
&lt;masonf> +1<br>
&lt;dandclark> +1<br>
&lt;emilio> +1<br>
&lt;tantek> 0<br>
&lt;emilio> RESOLVED: user agent styles can depend on appearance:base. Aim for eventual interoperability across all values of the property.<br>
&lt;gregwhitworth> Zakim, end meeting<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10028#issuecomment-2195094693 using your GitHub account


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

Received on Thursday, 27 June 2024 16:00:12 UTC