Re: [csswg-drafts] [css-anchor-position] Clarify computed value serialization for `anchor-scope` (#11774)

The CSS Working Group just discussed ``[css-anchor-position] Clarify computed value serialization for `anchor-scope` ``, and agreed to the following:

* `RESOLVED: the list of idents in anchor-scope are computed in the order specified`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> TabAtkins: anchor-scope is &lt;ident>#<br>
&lt;fantasai> TabAtkins: in practice it's a set, not a list -- order doesn't matter<br>
&lt;fantasai> TabAtkins: question was what order should it serialize in?<br>
&lt;fantasai> TabAtkins: fantasai argues that Computed value says "as specifies"<br>
&lt;fantasai> TabAtkins: Order needs to be well-defined enough to be specified<br>
&lt;fantasai> TabAtkins: so either need to define a sort order or use input order<br>
&lt;fantasai> TabAtkins: so suggestion is to use the input order<br>
&lt;fantasai> astearns: The only benefit in sorting the serialization is, if something is looking for style changes then the sorting would fail some false positives<br>
&lt;fantasai> astearns: but that's probably not useful enough to require sorting<br>
&lt;fantasai> TabAtkins: if you have allow-discrete transition, that would kick off a transition with no effect<br>
&lt;fantasai> astearns: so I'm fine with saying computed value is as specified<br>
&lt;TabAtkins> fantasai: yeah, i think the ideal computed value woudln't maintain the order, for this reason, but it's such an edge case to care about<br>
&lt;fantasai> astearns: Proposed resolution is the list of idents in anchor-scope are computed in the order specified<br>
&lt;fantasai> RESOLVED: the list of idents in anchor-scope are computed in the order specified<br>
</details>


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


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

Received on Thursday, 3 April 2025 17:18:55 UTC