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

Re: [csswg-drafts] [css-text][css-sizing] When to/not to include preserved trailing spaces (#3440)

From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
Date: Sat, 27 Jul 2019 12:02:03 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-515678991-1564228922-sysbot+gh@w3.org>
I don't see how that's relevant. How the updated proposal interacts with alignment is the same as the old one from fantasai, on which we had resolved with your approval, and reconfirmed in with you Toronto.

Again, the difference between the standing resolution (#3868) and my proposed tweak on it ( #4095) is limited to what happens to spaces before a forced break when they don't fit the line. Everything else is the same.

If we have `<div>a_b__</div>` with `white-space:pre-wrap` and a line length that will fit only 4 characters, the previous resolution results in:
```
|a_  |
|b__ |
```
My proposed change will result in:
```
|a_b_|_
```

That seems better because:
* it is more web compatible: the existing resolution would result in content that currently fits in one line to start taking two some times.
* If you consider editing, and you add a "c" at the end of the example above, both the existing resolution and my proposal will result in:
    ```
    |a_b_|_
    |c   |
    ```
   For my proposal, that's not surprising for the user, as the wrapping of the text before the inserted character doesn't change, but for the existing resolution, it is surprising, as the wrapping of the previous text would change.


-- 
GitHub Notification of comment by frivoal
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3440#issuecomment-515678991 using your GitHub account
Received on Saturday, 27 July 2019 12:02:05 UTC

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