W3C home > Mailing lists > Public > www-style@w3.org > January 2017

Re: [css-text] Collapsing whitespace at the end of a line

From: Pierre-Anthony Lemieux <pal@sandflow.com>
Date: Mon, 9 Jan 2017 20:44:02 -0800
Message-ID: <CAF_7JxDm4amga8O-8uJWAHHDG=fpUOTGaez0v1zeyncwam5ETA@mail.gmail.com>
To: fantasai <fantasai.lists@inkedblade.net>, "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: www-style list <www-style@w3.org>
> Why preserve the space before the break but not after it? o_O

I ran into this bizarre behavior issue while working on subtitle
rendering. See top example at:

   https://codepen.io/palemieux/pen/bgVJKO

The space before the line break remains, but not the one after.

I would think this is an implementation bug, unless there is a
historical reason.

> Well, sure, but wouldn't you want pre-wrap for those kinds of cases?

Yes. Any downsides to pre-wrap?

Best,

-- Pierre

On Sat, Jan 7, 2017 at 8:21 PM, fantasai <fantasai.lists@inkedblade.net> wrote:
> On 08/19/2016 07:23 PM, Tab Atkins Jr. wrote:
>>
>> On Wed, Aug 17, 2016 at 7:19 PM, fantasai <fantasai.lists@inkedblade.net>
>> wrote:
>>>
>>> On 09/10/2015 01:36 PM, Tab Atkins Jr. wrote:
>>>>
>>>>
>>>> According to <https://drafts.csswg.org/css-text/#collapse>, whitespace
>>>> preceding a segment break is removed.  However, it appears that
>>>> browsers instead collapse it to one space.
>>>>
>>>> Here's an example using 'white-space':
>>>>
>>>> <div style="white-space: pre-line;">a
>>>> z</div>
>>>>
>>>> (Just in case the email client trims things, there's a space at the
>>>> end of the first line, after the "a".)
>>>>
>>>> Here's an example using <br>:
>>>>
>>>> <div style="white-space: pre-line;">a <br>z</div>
>>>>
>>>> In both of these examples, if you highlight the "a" and then drag
>>>> slightly rightward, you'll see it highlight a space character as well.
>>>> This happens in both Chrome and Firefox.
>>>>
>>>> This sgugests that browsers are not following the "preceding" part of
>>>> step 1 in that section, and are instead falling down to step 4, where
>>>> runs of spaces are collapsed down to a single visible space.
>>>>
>>>> Is there a particular reason for this?  Should we adjust the spec to
>>>> match implementations, or file bugs on implementations to match the
>>>> spec?
>>>
>>>
>>> I'm inclined to file bugs on implementations to match the spec,
>>> since that seems like kinda weird behavior. Why preserve the
>>> space before the break but not after it? o_O
>>
>>
>> I don't particularly care either way, tho there are cases where
>> trailing whitespace has some significance - for example, illustrating
>> markdown examples (where two trailing spaces indicates a hard
>> linebreak).
>
>
> Well, sure, but wouldn't you want pre-wrap for those kinds of cases?
>
> [Testcase attached, fwiw.]
>
> ~fantasai
Received on Tuesday, 10 January 2017 04:44:56 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 10 January 2017 04:44:57 UTC