- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Wed, 01 Oct 2025 16:14:18 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed ``[css-anchor-position-1] Inconsistent naming of `position-area` values``, and agreed to the following: * `RESOLVED: accept jfkthame's proposal in the issue` <details><summary>The full IRC log of that discussion</summary> <kbabbitt> TabAtkins: right now the logical keywords in position-area have both container relative directions and self relative directions<br> <kbabbitt> ... we named the self ones by adding the word self into the keyword<br> <kbabbitt> ... logic we have for placing self ones is that it goes before logical part<br> <kbabbitt> ... [gives example]<br> <kbabbitt> ... was brought up by ? that this is difficult to predict where the self goes<br> <kbabbitt> ... sometimes start of keyword, sometimes middle depending on how many keywords are logical<br> <kbabbitt> ... would prefer something consisitent<br> <kbabbitt> ... I have no issue with this<br> <kbabbitt> s/?/jfkthame/<br> <kbabbitt> TabAtkins: propose we adopt jfkthame's proposal to move self consistently to the start of the keyword<br> <kbabbitt> astearns: to the portion of the value that is the logical keyword<br> <kbabbitt> TabAtkins: no, to the start of the keyword<br> <kbabbitt> ... right now it could be in the middle<br> <kbabbitt> astearns: oh his second set has self as the second clause<br> <fantasai> Currently it's x-self-start, suggestion is to change to self-x-start<br> <kbabbitt> TabAtkins: yes, the start of the direction part<br> <kbabbitt> astearns: yes<br> <kbabbitt> TabAtkins: proposal is as jfkthame said in the issue<br> <kbabbitt> astearns: Proposal is to accept jfkthame's proposal in the issue<br> <kbabbitt> fantasai: one caveat is that these have been implemented<br> <kbabbitt> ... but very rarely deployed<br> <kbabbitt> ... we don't expect a lot of use of these<br> <kbabbitt> astearns: so now is the time to make the change if we can<br> <kbabbitt> fantasai: yes<br> <kbabbitt> astearns: objections?<br> <kbabbitt> RESOLVED: accept jfkthame's proposal in the issue<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12749#issuecomment-3357137483 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 1 October 2025 16:14:19 UTC