You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[css-inline-3] text-edge-over/text-edge-under vs text-edge shorthand #5236
@dbaron raised the question of whether we need the longhands for text-edge, or just a shorthand. Are there use cases where it would be convenient to cascade them independently?
I am not convinced we need the longhands, but we should certainly have a shorthand. The simplest grammar would probably be this:
text-edge: leading | normal | <over-metric> <under-metric>
<over-metric>: text | cap | ex | ideographic | ideographic-ink
<under-metric>: text | alphabetic | ideographic | ideographic-ink
I suppose we could also make the second value optional, and map it to the same value as the first one in the cases where the pairs exist (text, ideographic, and ideographic-ink). What the implied second value would be if you picked cap or ex as the over side is less obvious though. Maybe cap, which is a broad metric, might be matched with text for the under side, while ex, which is a tight metric, would be with alphabetic.
Closing this issue without prejudice: if there ends up being use cases for longhands, someone can file a new issue and we can consider them at that point.
Activity
frivoal commentedon Jun 18, 2020
I am not convinced we need the longhands, but we should certainly have a shorthand. The simplest grammar would probably be this:
I suppose we could also make the second value optional, and map it to the same value as the first one in the cases where the pairs exist (
text,ideographic, andideographic-ink). What the implied second value would be if you pickedcaporexas the over side is less obvious though. Maybecap, which is a broad metric, might be matched withtextfor the under side, whileex, which is a tight metric, would be withalphabetic.fantasai commentedon Jun 18, 2020
I've drafted it up with longhands for now; defaulting missing keywords to
textbecause that's the safest.[css-inline-3] Remove text-edge-* longhands for now. #5236
fantasai commentedon Mar 28, 2025
Closing this issue without prejudice: if there ends up being use cases for longhands, someone can file a new issue and we can consider them at that point.