- From: r12a via GitHub <noreply@w3.org>
- Date: Fri, 17 Apr 2026 08:03:31 +0000
- To: public-css-archive@w3.org
I'm struggling to see how those factors are relevant. If an implementer has to implement, say, `trim-start`, they still need to know that this is going to affect: 1. the width of a paragraph-initial punctuation 2. the width of punctuation internal to a paragraph that is wrapped to the start of a line 3. the width of punctuation alongside other punctuation marks 4. the width of punctuation at the end of a line And code needs to flip the setting for each of those items as appropriate. Use of a combo keyword like `trim-start` is just a shorthand notation for a collection of settings that still have to be activated one by one, but there is an overhead imposed where the implementer has to recognise what constellation of settings is applied by each keyword before tweaking the settings. And, as i mentioned before, i and other tech-savvy people i have spoken with have to put in a significant effort to understand the differences between these pre-made combos, largely because to understand them you still need to first understand what are each of the aspects of the layout they potentially affect, but then you have to go further and compare and remember the combinations associated with each combo keyword, and what the keywords allow you to do and not do. Much simpler and for me more intuitive is to cut out that extra level and its confusions. That also gives the content author complete control over what they want to do, rather than telling them what you'll allow and what you won't. I think that content authors considering how lay out their text actually do think in terms of the 'low level' features, rather than recognising one of these combos that we just invented (and are still not completely confident about!). -- GitHub Notification of comment by r12a Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13789#issuecomment-4266361308 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 17 April 2026 08:03:32 UTC