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

[csswg-drafts] Pull Request: [css-text] Clarify handling of other space separators in white-space dfn

From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
Date: Thu, 03 Dec 2020 07:24:54 +0000
To: public-css-archive@w3.org
Message-ID: <pull_request.labeled-328089269-None-sysbot+gh@w3.org>
frivoal has just labeled a pull request from frivoal for https://github.com/w3c/csswg-drafts as "Closed Accepted as Editorial":

== [css-text] Clarify handling of other space separators in white-space dfn ==
The definition of the various values of the white-space property in
section 3 does not go into much detail about exactly how they work,
and just provides a high level intro to what they do. The details are
provided in section 4, and in particular 4.1 and 4.3 (so called
“phase 1” and “phase 2” of white space processing).

While this phase 2 has been updated (see https://github.com/w3c/csswg-drafts/issues/2500, https://github.com/w3c/csswg-drafts/issues/3879, or https://github.com/w3c/csswg-drafts/issues/4180)
to define that not only space characters, but also other space
separators hang / don't hang / wrap / don't wrap, etc, based on the
value of the white-space property, the high level definition of these
values was not updated to reflect that.

While this is not necessarily a bug, as it is already called out that
details are in section 4, apparent contradictions or omissions can be

Therefore, in the part of these definitions that explicitly talked
about white space wrapping/hanging (or not), include other space
separators as well, as defined in 4.3.

See https://github.com/w3c/csswg-drafts/pull/4420

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 3 December 2020 07:24:56 UTC

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