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

Re: [csswg-drafts] [css-text-3] Define break at space to remove a space explicitly (#4308)

From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
Date: Thu, 03 Oct 2019 01:00:03 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-537741933-1570064402-sysbot+gh@w3.org>
Actually, a little more testing shows that there's less interop than I thought:
https://jsbin.com/hijucaq/edit?html,css,output
Chrome:
![chrome](https://user-images.githubusercontent.com/113268/66091082-432d4580-e5c1-11e9-9a4b-2d7dbb94a06d.png)

----

Firefox:
![firefox](https://user-images.githubusercontent.com/113268/66091108-5b04c980-e5c1-11e9-8a20-153fbfc29ff8.png)

----

Safari:
![safari](https://user-images.githubusercontent.com/113268/66091114-63f59b00-e5c1-11e9-8fa4-f7565abc79a4.png)

----

Edge18:
![edge](https://user-images.githubusercontent.com/113268/66091123-6b1ca900-e5c1-11e9-9cd1-efd9ca309eaa.png)

----

In my opinion, different browsers get different aspects right. I agree with Chrome and Firefox for the behavior of `white-space:normal`, and mostly with Edge (except for the lack of hanging of the last space) or safari (except they clip the spaces they hang, which the spec does allow) for `white-space: pre-wrap`. In other words, here's what I think we should do:

<img width="218" alt="should" src="https://user-images.githubusercontent.com/113268/66091710-dbc4c500-e5c3-11e9-9462-3d39bdb81f9b.png">


-- 
GitHub Notification of comment by frivoal
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4308#issuecomment-537741933 using your GitHub account
Received on Thursday, 3 October 2019 01:00:05 UTC

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