- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 29 Mar 2023 16:15:27 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-text-4] white-space:break-spaces is in level 3 but not level 4`, and agreed to the following: * `RESOLVED: Add break-spaces to white-space-collapse` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> fantasai: part of merging level 3 into 4 is making sure we integrated all the level 3 changes<br> <TabAtkins> fantasai: level 4 split white-space into two longhands<br> <TabAtkins> fantasai: We didn't have a place to host the break-spaces value<br> <TabAtkins> fantasai: So currently we put it as a value on white-space-collapse<br> <florian> q+<br> <Rossen_> ack florian<br> <TabAtkins> florian: Two positives, one negative<br> <fantasai> https://drafts.csswg.org/css-text-4/#white-space-collapsing<br> <TabAtkins> florian: In terms of behavior I think this is the right longhand.<br> <TabAtkins> florian: In naming, having same keyword in shorthand and longhand is nice<br> <TabAtkins> florian: But in the context of this longhand, the name isn't intuitive.<br> <TabAtkins> florian: We could rename, but then it would be differnet keyword between shorthand and longhand<br> <TabAtkins> florian: So I think the current spec is the right compromise, but it is a compromise<br> <fantasai> white-space-collapse: collapse | preserve | preserve-breaks | preserve-spaces | break-spaces<br> <chrishtr> rossen: yes 8637, thanks<br> <TabAtkins> fantasai: Agree it's a little awkward in naming, since we only break spaces if we *are* wrapping, which is controlled by another property. It's more like "preserve-breakable-spaces", but that gets longer.<br> <TabAtkins> Rossen_: Is there anything preventing us from resolving?<br> <TabAtkins> Rossen_: Objections?<br> <TabAtkins> fantasai: proposed resolution is to add break-spaces to white-space-collapse<br> <TabAtkins> RESOLVED: Add break-spaces to white-space-collapse<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3794#issuecomment-1488909969 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 29 March 2023 16:15:29 UTC