W3C home > Mailing lists > Public > public-css-archive@w3.org > August 2020

Re: [csswg-drafts] [css‑text‑4] Multi‑value `white‑space` syntax proposal (#5382)

From: Mike Bremford via GitHub <sysbot+gh@w3.org>
Date: Sun, 02 Aug 2020 10:29:47 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-667656410-1596364186-sysbot+gh@w3.org>
Thanks for suggesting this - I agree, this is a good idea for several reasons:

1. It's consistent with how other shorthand properties are handled.
2. It gives forward compatibility for the `white-space` property. If we don't do this, the `white-space` will be able to set some combinations of its components, but not all. This will eventually lead to be becoming a sort of legacy property, which I don't think we want.
3. It's removing one level of magic from the shortcuts - "pre" is just s shorter way of writing "preserve none nowrap", which is easier to explain than saying it sets `text-space-collapse` to preserve, `text-space-trim` to none and `text-wrap` to no-wrap.

I'm unconvinced on the value of renaming "nowrap" to "no-wrap" as part of this move - in particular, because it would make both `white-space: nowrap` and `white-space: no-wrap` evaluate to the same result. This could lead to a very confusing transition period until css-text-4 is fully implemented. But otherwise, great idea.

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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 2 August 2020 10:29:49 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:13 UTC