W3C home > Mailing lists > Public > www-style@w3.org > November 2015

Re: [css-text] pre-wrap / pre-wrap-auto

From: Koji Ishii <kojiishi@gmail.com>
Date: Sat, 21 Nov 2015 16:15:58 +0900
Message-ID: <CAN9ydbXw+JoT=AKUnd0j53x8Oj=_9v=NT4q1TU189nQeRpu1Ag@mail.gmail.com>
To: Florian Rivoal <florian@rivoal.net>
Cc: fantasai <fantasai.lists@inkedblade.net>, "www-style@w3.org" <www-style@w3.org>
2015-11-20 16:08 GMT+09:00 Florian Rivoal <florian@rivoal.net>:

>
> > Do you have any example sites/applications that do all (a)-(e)?
>>
>> Offline: The "Notes" application on OS X has all of (a) to (e)
>>
>
> Do you mean Notes.app? I see Notes.app does the same as Chrome; i.e., not
> (b) nor (e). What are we seeing differently? I'm running 10.11.
>
>
> Yes, I mean Notes.app. I'm on OS X 10.10.5 if it makes a difference.
>
> Based on this example, I find that it does all of a to e.
>
> http://florian.rivoal.net/csswg/wrap/notes-app.png
>
> In what way does it not do that?
>

Mine does what Safari does, so maybe they changed in 10.11. Notes in 10.11
is a major upgrade.

One more thing I tested[1]; so the behavior on IE/FF is only for textarea,
> not for normal div, nor for contenteditable.
>
> [1] http://output.jsbin.com/lopave/
>
>
> You forgot "word-wrap: break-word;" It's in the UA stylesheet for
> textareas, but not for divs. If you put it in, FF gives the same behavior
> on textareas and divs. IE doesn't.
>
>
> And if you also add: "word-break:break-all" you get the behavior you
> described as your favorite one for code editors and terminals.
>

Added, but I still don't see Firefox does (b).

I've tried to explain multiple times (many mails, some short, some long,
> multiple conf calls, f2f...) what I want to solve and why, but it seems I'm
> not getting my point across, so let's try another angle. Since you're
> reopening the case after we had a WG resolution, can you clarify what your
> goal is?
>

I've tried too, unfortunate to fail to even understand each other. I'm
against the combination of a+b+c+d+e.

1. I want to understand what user problem you're trying to solve. Real use
cases? User complaints?
2. I believe what you're proposing makes editing experiences much worse. To
prove I'm wrong:
2.1. I want to see single apps/sites that does what you're proposing.
2.2. I want to see what other editor developers think to understand how
common the proposed behavior is.

/koji
Received on Saturday, 21 November 2015 07:16:46 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:58 UTC