Re: [csswg-drafts] [css-anchor-position] position-area specified vs. computed value is weird (#12759)

The CSS Working Group just discussed `[css-anchor-position] position-area specified vs. computed value is weird`, and agreed to the following:

* `RESOLVED: close no change`

<details><summary>The full IRC log of that discussion</summary>
&lt;ydaniv> emilio: position-area has no reason for changing its computed value, and what we're doing is weird<br>
&lt;ydaniv> ... I have a preference if it both are consistent<br>
&lt;ydaniv> TabAtkins: right now the position-area is logical, and we do a canonicalization of speicifc set of keywords<br>
&lt;ydaniv> ...  emilio says we can do that early so it's always in the right form<br>
&lt;ydaniv> ... we propose we leave that alone in a number of properties<br>
&lt;ydaniv> ... the big thing is we don't do canonicaliztion at compute value time<br>
&lt;ydaniv> ... I'm leaning against this<br>
&lt;ydaniv> fantasai: same position as TabAtkins, and current rules are what's implemented at WebKit<br>
&lt;ydaniv> astearns: and Gecko<br>
&lt;ydaniv> emilio: I'm ok with no change<br>
&lt;ydaniv> PROPOSED RESOLUTION: close no change<br>
&lt;ydaniv> astearns: objections?<br>
&lt;fantasai> [Tab pointed out that this allows authors to interact with the value as they specified is]<br>
&lt;ydaniv> RESOLVED: close no change<br>
&lt;fantasai> s/is/it/<br>
</details>


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


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

Received on Wednesday, 21 January 2026 16:33:37 UTC