Re: [csswg-drafts] [css-anchor-position] Computed value of `position-area` (#11828)

The CSS Working Group just discussed ``[css-anchor-position] Computed value of `position-area` ``, and agreed to the following:

* `RESOLVED:  block/inline-start-end (and the self-* variants) compute to start/end or self-start/end`

<details><summary>The full IRC log of that discussion</summary>
&lt;bkardell> TabAtkins: the position-area property has a number of syntaxes - it has two that are exactly equivalent<br>
&lt;TabAtkins> start start and `block-start inline-start`<br>
&lt;bkardell> elika said they should be equivalent, tab doesn'thavean opinion<br>
&lt;bkardell> TabAtkins: which of the pair it should go to elika? opinion?<br>
&lt;fantasai> astearns: Should it be the shortest serialization or the most explicit one?<br>
&lt;bkardell> kiet: I opened this - It comes up because I am implementing and some of the tests are mismatched because webkit serializes one way, chrome another - if we have one way it's easier to write tests<br>
&lt;bkardell> florian: make it short if we can<br>
&lt;bkardell> TabAtkins: if it is already the case that multiple browsers do this, but just disagreeonwhich I would agree and say lets just use start start<br>
&lt;bkardell> Proposed resolution: block-start and inline-start will serialize to start start and they will compute to start start<br>
&lt;bkardell> kiet: this also applies to self block start...?<br>
&lt;bkardell> TabAtkins: yes<br>
&lt;TabAtkins> proposed: block/inline-start-end (and the self-* variants) compute to start/end or self-start/end<br>
&lt;bkardell> resolved<br>
&lt;bkardell> resolved:  block/inline-start-end (and the self-* variants) compute to start/end or self-start/end<br>
&lt;bkardell> RESOLVED:  block/inline-start-end (and the self-* variants) compute to start/end or self-start/end<br>
&lt;bkardell> !!!!<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11828#issuecomment-2776447178 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:11:52 UTC