- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Thu, 01 Dec 2016 05:27:59 +0000
- To: public-css-archive@w3.org
Hmmm. I'm a bit confused. What you're saying seem to be arguments supporting what I proposed (“leaning toward[...]”) or something close, but I can't really tell if you are indeed supporting it or explaining why you think we need something else. > (1) authors can demand a stable algorithm for an element/subtree so that starting to edit doesn't cause a reflow; that'd be `text-wrap: wrap`, for which we'd require greedy line breaking > (2) page authors/designers can express that good line-breaking is important That'd be `text-wrap: multi-line`, for which we'd recommend the algo you're suggesting, but also allow UAs to do other stuff (Knuth-Plass or what have you). > As Fantasai said when it was discussed before, authors should not have to opt in to higher quality. That'd be `text-wrap: auto`, the initial value, which would the UA could do anything, but we could suggest doing the same as `text-wrap: wrap` on editable elements and the same as text-wrap: multi-line` elsewhere. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/672#issuecomment-264082348 using your GitHub account
Received on Thursday, 1 December 2016 05:28:06 UTC