Re: [csswg-drafts] [css-inline-3] The behavior when one value is specified for `text-box-edge` (#10703)

Thanks for including me on this, and sorry for what seems like initial confusion in this issue. Just to clarify, I am not proposing the change the default bottom edge for all values to `alphabetic`.

The point I am making in the [linked comment] is that when a user opts to trim to `cap` or `ex` that should be the outcome. Both of these terms are measured from what has been defined in CSS as the "alphabetic baseline", so setting either `cap` or `ex` and not having the correct bottom edge is actually misleading.

I would propose that the outcome for single value text edges be as follows:

![Preview of CSS text-edge proposals](https://github.com/user-attachments/assets/88771464-7a0f-4b21-924c-167e70b69fff)

With the following updates to the value definitions in [the spec]:

| Edge | Definition |
| --- | --- |
|`text`| Use the [text-over baseline] as the [over] edge and [text-under baseline] as the [under] edge. |
|`cap`| Use the [cap-height baseline] as the [over] edge and [alphabetic baseline] as the [under] edge. |
|`text`| Use the [x-height baseline] as the [over] edge and [alphabetic baseline] as the [under] edge.  |


[linked comment]: https://github.com/seek-oss/capsize/issues/205#issuecomment-2185365588
[the spec]: https://drafts.csswg.org/css-inline-3/#text-edges
[text-over baseline]: https://drafts.csswg.org/css-inline-3/#text-over-baseline
[text-under baseline]: https://drafts.csswg.org/css-inline-3/#text-under-baseline
[over]: https://drafts.csswg.org/css-writing-modes-4/#over
[under]: https://drafts.csswg.org/css-writing-modes-4/#under
[cap-height baseline]: https://drafts.csswg.org/css-inline-3/#cap-height-baseline
[x-height baseline]: https://drafts.csswg.org/css-inline-3/#x-height-baseline
[alphabetic baseline]: https://drafts.csswg.org/css-inline-3/#alphabetic-baseline

-- 
GitHub Notification of comment by michaeltaranto
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10703#issuecomment-2282932140 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Sunday, 11 August 2024 23:56:37 UTC