- From: Jen Simmons via GitHub <sysbot+gh@w3.org>
- Date: Tue, 01 Apr 2025 13:12:52 +0000
- To: public-css-archive@w3.org
To summarize: Currently, if an author only includes one value for `text-box-edge`, the specification says this should be invalid. Instead let's resolve that declaring only one value is valid, and the undeclared edge reverts to `auto`. This will mean that when the author only includes one value, the following happens: - `text` becomes `text text` - `ideographic` becomes `ideographic ideographic` - `ideographic-ink` becomes `ideographic-ink ideographic-ink` - `cap` becomes `cap auto` - `ex ` becomes `ex auto` - `alphabetic ` becomes `auto alphabetic ` While making this change could have unintended consequences for the unskilled author (they write `cap` expecting `cap alphabetic` and the end line ends up as `auto` instead), it's much better overall. Authors who only write one edge (like `text-box: trim-start cap`) will get the result they want, instead of ending up with nothing happening (because it's invalid). (And the authors who did expect `cap alphabetic` can figure out that's not what they got because that's not what they wrote. Realizing the browser defaulted to `auto` will feel natural.) Doing this will make using `text-box` much simpler, and much easier to teach. If authors are required to specify both edges, they have to understand the entire line box model. If they can just write one edge, they can memorize a few "tricks" to do the things they want to do most, and not worry about the rest. > Is alphabetic more intuitive default for cap and ex than text or auto? I do not believe that _most_ use cases for `cap` also involve `alphabetic`. There are a lot of use cases where an author will want to only trim the `cap`/`ex` edge, or only trim the `alphabetic` edge. There are also a lot of use case where they will want to trim both. But it's like 50/50. Not 99%/1%. The browser should simply do what the author says. If they want both, they need to write both. If they write just one, they get just one. -- GitHub Notification of comment by jensimmons Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11460#issuecomment-2769319469 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:12:53 UTC