Re: [csswg-drafts] [css-ui-4] Align canonical order of `outline` sub-properties with `border` (#7700)

The CSS Working Group just discussed ``[css-ui-4] Align canonical order of `outline` sub-properties with `border` ``.

<details><summary>The full IRC log of that discussion</summary>
&lt;dbaron> TabAtkins: Guillaume noted that despite similar value spaces, the outline and border have a different order of the value definition grammar, and since we generally follow value definition order when serializing.<br>
&lt;dbaron> TabAtkins: fantasai notes that in CSS2 the grammar order wasn't implied to have a meaning.<br>
&lt;dbaron> TabAtkins: since we do rely on the grammar order for things it would make sense to align them<br>
&lt;dbaron> TabAtkins: Aside from that possibility, I think it's reasonable to align the 2, more likely to follow what border does.<br>
&lt;dbaron> TabAtkins: I think we should resolve to make outline's component order match border's component order.<br>
&lt;fantasai> Note that at least two people filed this issue, since we have a dup<br>
&lt;astearns> ack dbaron<br>
&lt;TabAtkins> dbaron: In the past I was always concerned about the model of defaulting to the syntax in the value definition<br>
&lt;TabAtkins> dbaron: I think in general it is worth explicitlyt esting impls to see what they do and then coming back<br>
&lt;emilio> +1 dbaron<br>
&lt;TabAtkins> dbaron: Partaly I'm guessing impls dont' formally follow the spec right now<br>
&lt;TabAtkins> dbaron: They wer eimplemented before we created this rule, and probably haven't udpated<br>
&lt;TabAtkins> dbaron: So probably tests might show some accidental compliance anyway<br>
&lt;TabAtkins> astearns: Would you like to test then resolve? Or okay to resolve first and use tests to verify?<br>
&lt;TabAtkins> dbaron: Probably good to get tests first, but should be fine to resolve async once we do.<br>
&lt;tantek> +1 on getting tests first, this has been implemented long enough ago that it's worth gathering that data first<br>
&lt;TabAtkins> astearns: Sounds good, let's see if we can resolve async once we ahve the data<br>
</details>


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


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

Received on Wednesday, 22 February 2023 18:00:54 UTC