W3C home > Mailing lists > Public > public-css-archive@w3.org > November 2016

Re: [csswg-drafts] [css-text-4] Allow for paragraph-level line breaking

From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
Date: Thu, 03 Nov 2016 04:03:55 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-258060553-1478145833-sysbot+gh@w3.org>
Point taken about performance. However I think if we introduce a 
switch, it should be between auto and on, not between off and on: CSS 
UAs generally do greedy line breaking as the default, and that's ok, 
but if an implementer wants to provide a better default (e.g. it is a 
print UA not concerned with performance, or it has a 
not-great-but-better-than-greedy algorithm that performs fine...), 
that should be allowed.

With that in mind:
* Do we want that switch at all, or should it be left to houdini? I 
think this should be baked in CSS. Certainly houdini APIs should be 
capable of supporting this, but doing it right in an i18n context is 
hard and tedious, and I don't think putting that burden on authors is 
* Do we want `auto | on` or `auto | on | off`, where `off` explicitly 
requires greedy line breaking? I don't think `off` is needed, but I 
could be wrong. Authors do not know enough about the performance 
tradeoff that this implies to make an informed decision (other than by
 assuming a particular version of a particular browser), and if they 
need to depend on a certain wrapping behavior, there's `white-space: 
* Do we want to be able to switch between multiple forms of smart line
 breaking? If the answer is “yes, but not until a later level”, does 
that still influence how we design the property?

GitHub Notification of comment by frivoal
Please view or discuss this issue at 
using your GitHub account
Received on Thursday, 3 November 2016 04:04:02 UTC

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