Re: [csswg-drafts] [css-anchor-position-1] `position-area`: `self` keyword inconsistency (#11371)

The CSS Working Group just discussed ``[css-anchor-position-1] `position-area`: `self` keyword inconsistency``, and agreed to the following:

* `RESOLVED: x-self-start and self-block-start are correct, fix the spec`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> TabAtkins: We have both normal logical keywords and self-* logical keywords<br>
&lt;fantasai> TabAtkins: using either containing block writing mode or box's own writing mode<br>
&lt;fantasai> TabAtkins: Kiet pointed out that there's an inconsistency in the keywords about the placement of 'self'<br>
&lt;fantasai> TabAtkins: This was intentional on our part, because self- is not modifying the axis, but the direction<br>
&lt;fantasai> TabAtkins: x-self-start is combining physical direction and logical direction<br>
&lt;fantasai> TabAtkins: whereas self-inline-start is using self writingmode for both axis and direction<br>
&lt;fantasai> Kiet: Wanted to understand why it's the case. once I read Tab's comment, it makes sense<br>
&lt;fantasai> Kiet: So I think it's fine to keep it like that<br>
&lt;fantasai> Kiet: Another issue which is editorial is, in some places we use self-block and other places we use block-self<br>
&lt;fantasai> TabAtkins: Oh, indeed we do!<br>
&lt;fantasai> astearns: Is it just in anchorpos spec or others?<br>
&lt;fantasai> TabAtkins: just here<br>
&lt;fantasai> TabAtkins: but that is definitely an editorial mistake<br>
&lt;fantasai> fantasai: That raised the question of what was intended.<br>
&lt;fantasai> TabAtkins: Ohh, yeah.<br>
&lt;fantasai> TabAtkins: I think it still needs to be self-block-start, since it's interpreting the axis also per the self writing mode<br>
&lt;fantasai> TabAtkins: ...<br>
&lt;fantasai> TabAtkins: We did a copy-paste error probably<br>
&lt;ntim> I heard block as a verb :D<br>
&lt;ntim> block self start<br>
&lt;fantasai> astearns: Is that an argument to make the change?<br>
&lt;fantasai> TabAtkins: just an editing error<br>
&lt;fantasai> TabAtkins: more general argument that self-{block-start} is what we have here<br>
&lt;fantasai> TabAtkins: other way around could imply you're taking the axis (block) from the container and the direction (start) from the self<br>
&lt;fantasai> RESOLVED: x-self-start and self-block-start are correct, fix the spec<br>
</details>


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