- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Tue, 01 Apr 2025 13:55:27 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-inline-3] -top/-bottom vs -over/-under`, and agreed to the following: * `RESOLVED: use -top and -bottom as the direction suffix for all keywords in this property (referring to over/under)` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> fantasai: in 10713 we resolved to add reorderable kewyrods to text-box-edge<br> <TabAtkins> fantasai: i didn't edit that into the spec yet because i ran into this issue<br> <TabAtkins> fantasai: what keywords do we actually want<br> <TabAtkins> fantasai: in horizontal text top/bottom are pretty obvious. we ahve text-top/text-bottom etc<br> <TabAtkins> fantasai: when you have vertical it's more interesting<br> <bkardell> s/kewyrods/keywords<br> <TabAtkins> fantasai: in our specs, and in things like ruby-position, we use the terms over/under to refer to "above the baseline" and "below the baseline"<br> <TabAtkins> fantasai: so what keywords do we want to use for text-edge? top/bottom, or over/under, or a mix? text-top and ideographic-over?<br> <TabAtkins> fantasai: murakami-san proposed we be consistent with top/bottom keywords we have already.<br> <TabAtkins> fantasai: i don't have a strong opinion, we just need to resolve on that<br> <TabAtkins> florian: so that would be consistent with the opentype naming?<br> <TabAtkins> fantasai: so over is sometimes top, sometimes left, sometime sright, depending on WM<br> <TabAtkins> fantasai: top in CSS, aside from vertical-align, is always page top<br> <TabAtkins> fantasai: but in vertical-align it's the over/udner side<br> <TabAtkins> fantasai: which can be left/right<br> <TabAtkins> TabAtkins: i was just confused, i thought florian was saying the opentype "top" wasn't always the css "over"<br> <TabAtkins> fantasai: no, it's always the same<br> <TabAtkins> jensimmons: so everyone's consistent that "top" isn't always top<br> <TabAtkins> astearns: and we can always go with top/bottom for now and always add over/under in the future as aliases if we need to<br> <TabAtkins> fantasai: yeah we could<br> <TabAtkins> florian: don't expect we'll need to tho<br> <TabAtkins> astearns: so proposed resolution is we stay with text-top/text-bottom?<br> <TabAtkins> fantasai: -top and -bottom for all keywords in this property<br> <TabAtkins> astearns: objection?<br> <TabAtkins> RESOLVED: use -top and -bottom as the direction suffix for all keywords in this property (referring to over/under)<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11365#issuecomment-2769447415 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 1 April 2025 13:55:28 UTC