W3C home > Mailing lists > Public > public-css-archive@w3.org > April 2019

[csswg-drafts] [css-text] Hanging/collapsing of fixed-width spaces not specified (#3879)

From: Brian Smith via GitHub <sysbot+gh@w3.org>
Date: Sat, 27 Apr 2019 10:40:42 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-437930615-1556361641-sysbot+gh@w3.org>
briansmith has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-text] Hanging/collapsing of fixed-width spaces not specified ==
https://www.w3.org/TR/css-text-3/#white-space-rules says "White space processing in CSS affects only the document white space characters: spaces (U+0020), tabs (U+0009), and segment breaks."

However, it is often/usually desirable for the collapsing/hanging behavior to apply to fixed-width spaces when the fixed-width space would cause a line break. Consider:

```html
<p>1&#x205f;+&#x205f;1&#x2005;=&#x2005;2</p>
```
Which renders as:
> <p>1&#x205f;+&#x205f;1&#x2005;=&#x2005;2</p>

The spaces on either side of the `+` are U+205F Medium Mathematical Space and the spaces on either side of the `=` are U+2005. (This is the spacing recommended in http://www.unicode.org/notes/tn28 for these operators.)

Lines wrap at fixed-width spaces already (at least in the browsers I tested). However, in the browsers I tested, these fixed-width spaces do not currently collapse or hang like U+0020. Either collapsing/hanging of these spaces like U+0020 should be the default behavior, or there should be some way to opt into them being treated like U+0020 for the purposes of collapsing/hanging.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3879 using your GitHub account
Received on Saturday, 27 April 2019 10:40:44 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:46 UTC