- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Thu, 02 Feb 2023 00:22:47 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-text] text-spacing is very complicated`, and agreed to the following: * `RESOLVED: Accept the proposal in the issue to split text-spacing into longhands.` <details><summary>The full IRC log of that discussion</summary> <fantasai> -> https://github.com/w3c/csswg-drafts/issues/4246#issuecomment-1404738513<br> <TabAtkins> florian: myles said this prop is too complicated - too many values interacting in too many ways<br> <TabAtkins> florian: fantasai and i agree<br> <TabAtkins> florian: We proposed a shorthand/longhand combo of syntax that hopefully reduces the space fo syntax and limits it to a useful subset of behavior<br> <TabAtkins> florian: Proposal is in issue, might still be some bikeshedding<br> <myles> before: normal | none | auto | no-compress || [ trim-start | space-start | space-first ] || [ trim-end | space-end | allow-end ] || [ trim-adjacent | space-adjacent ] || ideograph-alpha || ideograph-numeric || punctuation<br> <TabAtkins> Rossen_: What simplification do we want to draw attention to?<br> <myles> after: text-spacing: normal | none | auto | <'text-autospace'> || <'text-spacing-trim'><br> <myles> text-spacing-trim: auto | space-all | trim-all | [ allow-end || space-first ]<br> <myles> text-autospace: normal | auto | no-autospace |<br> <myles> [ ideograph-alpha || ideograph-numeric || punctuation ]<br> <myles> || [ insert | replace ]<br> <TabAtkins> fantasai: We split the prop into two longhands - text-spacing-trim and text-auto-space<br> <TabAtkins> fantasai: t-s-t is about trimming the blank half of full-width spacing in various cases<br> <TabAtkins> fantasai: t-a-t adds extra space in certain places<br> <TabAtkins> fantasai: We removed all the combos except for the ones we believe woudl actually be used, from t-s-t<br> <TabAtkins> fantasai: There were three props controlling start/mid/end individually, but most combos won't be used<br> <TabAtkins> fantasai: So we reduced the syntax sapce of what keywords are allowed to be combined. If we want to extend in the future that's possible.<br> <TabAtkins> fantasai: for t-a-s: we added insert/remove keywords which we can discuss in another issue<br> <TabAtkins> fantasai: Controls whether you only insert space where there's none, or if you can repalce adjacent space with the correct amount of spacing<br> <TabAtkins> fantasai: Could split this into a pair of properties too, controlling inserting vs adjusting, but for now they're together<br> <TabAtkins> fantasai: And text-spacing is a shorthand for these that takes all the props<br> <TabAtkins> myles: This seems like a good place to start iterating.<br> <TabAtkins> myles: we think we can start implementing as the bare minimum form<br> <TabAtkins> myles: we just resolved on the initial value - it's unclear how that will be represented with these two props. assume that's an oversight<br> <TabAtkins> florian: In old version there was a set of values for start/mid/end. space-first set the start.<br> <TabAtkins> florian: Here space-first is a variation on trim-all that trims everywhere but space at the first.<br> <TabAtkins> fantasai: Details are in the description. If you like it we can edit it into the spec.<br> <TabAtkins> myles: I think it's an improvement on what was there before.<br> <TabAtkins> Rossen_: Hearing no objections.<br> <TabAtkins> RESOLVED: Accept the proposal in the issue to split text-spacing into longhands.<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4246#issuecomment-1412954153 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 2 February 2023 00:22:49 UTC