Re: [csswg-drafts] [css-values] Inconsistent position serialization (#2274)

The CSS Working Group just discussed `[css-values] Inconsistent position serialization`, and agreed to the following:

* `RESOLVED: Revert the previous resolution and the serialization for spec value is a 3-value serialization`

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> vmpstr, yeah, we'll spec it to just be an OR between the two aliases for each option<br>
&lt;dael> fantasai: We dug through a lot of serialization issues in the past. most edited in. There was some edits for backgrounds to handle 3-value syntax that's not allowed outside of bg-position<br>
&lt;dael> fantasai: Decided we would forse 3 value to 4 value. Looking at impl we noticed we have interop with 3-value serialized as 3-value. Note this is for for computed values. For specified when serialized out all browsers are serializing out as 3 values<br>
&lt;dael> fantasai: Prop reverting previous resolution and keep what browsers are doing now<br>
&lt;dael> astearns: Mainly b/c this is not a big enough deal to force a change?<br>
&lt;dael> fantasai: Yeah, we don't have actual problems with serialization. If you try and take it and put it into a different property there might be problems, but don't do that you're fine. Or grab the computed value and it works.<br>
&lt;dael> astearns: Comments?<br>
&lt;dael> astearns: Prop: Revert the previous resolution and the serialization for spec value is a 3-value serialization<br>
&lt;dael> astearns: Obj?<br>
&lt;dael> RESOLVED: Revert the previous resolution and the serialization for spec value is a 3-value serialization<br>
</details>


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


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

Received on Wednesday, 1 November 2023 23:12:03 UTC