- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Fri, 31 Jan 2025 21:48:05 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-gaps-1] Naming bi-directional gap decoration shorthand`, and agreed to the following: * `RESOLVED: rename gap-rule to 'rule'` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> kbabbitt: this came up in TAG review for gap decos<br> <TabAtkins> kbabbitt: there's a gap-rule shorthand that sets width/style/color for both directions<br> <TabAtkins> kbabbitt: named it gap-rule for a few reasons<br> <TabAtkins> kbabbitt: first, nervous about taking rule-* for future<br> <lea> q+<br> <TabAtkins> kbabbitt: also avoiding confusion between the "rule" properties and CSS rules<br> <TabAtkins> kbabbitt: just wanted some opinions<br> <TabAtkins> lea: this is what we do for gap - row-gap/column-gap, and gap<br> <TabAtkins> lea: so suggested doing the same and getting just 'rule'<br> <TabAtkins> lea: but you raise valid points<br> <TabAtkins> astearns: i'm usually very concerned about consistency, but not concerned in this case. i do like the guarding considerations.<br> <TabAtkins> TabAtkins: same<br> <TabAtkins> TabAtkins: so proposed resolution is stick with gap-rule?<br> <TabAtkins> fantasai: feels like it should be a longhand of 'gap' then, so i'm leanign the other way<br> <TabAtkins> kbabbitt: could it be? could get ambiguous, a length could be the gap size or the rule size<br> <TabAtkins> grule<br> <TabAtkins> florian: the confusion between decorative and syntactic rules is unlikely to anywhere besides these meetings, so it's fine<br> <TabAtkins> florian: and context is different enough anyway, not very confusing<br> <TabAtkins> fantasai: oh so i'm not suggesting `gap` be a shorthand that includes gap-rule, i suggest just doing 'rule'<br> <TabAtkins> astearns: so proposed resolution, rename gap-rule to 'rule'<br> <TabAtkins> RESOLVED: rename gap-rule to 'rule'<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11495#issuecomment-2628456343 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 31 January 2025 21:48:06 UTC