Re: [csswg-drafts] [css-anchor-position] Naming of the `inside` and `outside` `<anchor-side>` values (#11052)

The CSS Working Group just discussed ``[css-anchor-position] Naming of the `inside` and `outside` `<anchor-side>` values``, and agreed to the following:

* `RESOLVED: Close no change`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> TabAtkins: Right now, for generic side names, we use keywords inside / outside<br>
&lt;fantasai> TabAtkins: map to left/right/top/bottom depending on whether it puts anchored item inside the anchor or outside the anchor<br>
&lt;fantasai> TabAtkins: e.g. left: anchor(outside); puts the anchored item outside the anchor, i.e. to the right of the anchor<br>
&lt;fantasai> TabAtkins: jwatt felt these keywords were not super clear and suggested some alternatives<br>
&lt;kizu> q+<br>
&lt;fantasai> TabAtkins: Personally I think inside / outside are pretty fine<br>
&lt;fantasai> TabAtkins: and also these names have been deployed, so unless a strong reason to change, propose to close no change<br>
&lt;astearns> ack kizu<br>
&lt;fantasai> kizu: I think I still like inside / outside more than anything proposed<br>
&lt;fantasai> kizu: given we also have interop thing, we should keep it as-is<br>
&lt;jwatt> I don't have a strong opinion<br>
&lt;fantasai> astearns: objections to closing no change?<br>
&lt;fantasai> RESOLVED: Close no change<br>
</details>


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