Just as a side question: is this and the headlines feature too opinionated to become part of user-agent stylesheets? I’m not immediately saying it should be, I’m just curious if this was considered?
On Wed, Jun 21, 2023 at 17:49 Koji Ishii <ko...@chromium.org> wrote: > Sorry, filed here: https://github.com/w3ctag/design-reviews/issues/864 > > I thought the previous review covered this, but you're right that it > didn't cover other values of `text-wrap`. > > On Thu, Jun 22, 2023 at 12:25 AM Alex Russell <slightly...@chromium.org> > wrote: > >> Why was a TAG review not filed? >> >> On Wednesday, June 21, 2023 at 7:51:48 AM UTC-7 Koji Ishii wrote: >> >>> Contact emailsko...@chromium.org >>> >>> ExplainerNone >>> >>> Specification >>> https://drafts.csswg.org/css-text-4/#valdef-text-wrap-pretty >>> >>> Design docs >>> >>> https://docs.google.com/document/d/1jJFD8nAUuiUX6ArFZQqQo8yTsvg8IuAq7oFrNQxPeqI/edit?usp=sharing >>> >>> Summary >>> >>> Adjusts line breaking to avoid a short single word on the last line >>> (also known as typographic orphans.) When `text-wrap: pretty` is specified, >>> paragraphs that will end up with a short single word on the last line are >>> adjusted so that the last line has two or more words. The algorithm is >>> based on the Knuth-Plass algorithm, as used by TeX. It computes scores for >>> all candidates, and chooses the best one. To balance between the >>> typographic benefits and the performance impacts, it adjsuts the last 4 >>> lines of paragraphs that meet certain conditions. >>> >>> >>> Blink componentBlink>Layout>Inline >>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ELayout%3EInline> >>> >>> TAG reviewNone >>> >>> TAG review statusNot applicable >>> >>> Risks >>> >>> >>> Interoperability and Compatibility >>> >>> Low. This value only sets a bias for better layout over speed, without >>> any particular requirements. Browsers that don't support this value will >>> fall back to their default line breaking algorithm, but both the exact line >>> breaking results for this value and for the default value are not defined. >>> >>> >>> *Gecko*: Positive (https://bugzilla.mozilla.org/show_bug.cgi?id=630181) >>> >>> *WebKit*: Positive (https://github.com/w3c/csswg-drafts/issues/672) >>> This property is originally requested by an WebKit engineer. >>> >>> *Web developers*: Positive ( >>> https://clagnut.com/blog/2424#:~:text=the%20specification%20is-,text%2Dwrap%3Apretty,-.%20If%20it%E2%80%99s%20ever) >>> When Blink shipped `text-wrap: balance` that improved headlines, many >>> tweets and articles are seen on the web, wanting the feature to avoid a >>> single word on the last line (typographic orphans) for body text. >>> https://medium.com/swlh/typographic-orphans-on-the-web-266e32f756fe has >>> a simple JS solution to avoid typographic orphans. >>> https://github.com/robertknight/tex-linebreak is a JS implementation of >>> the Knuth-Plass algorithm, has 111 stars. >>> >>> *Other signals*: >>> >>> Ergonomics >>> >>> Another related value of this property `text-wrap: balance` improves >>> line breaking for headlines, while this value improves typography for body >>> text. >>> >>> >>> WebView application risks >>> >>> Does this intent deprecate or change behavior of existing APIs, such >>> that it has potentially high risk for Android WebView-based applications? >>> >>> None. >>> >>> >>> Debuggability >>> >>> >>> >>> Will this feature be supported on all six Blink platforms (Windows, Mac, >>> Linux, Chrome OS, Android, and Android WebView)?Yes >>> >>> Is this feature fully tested by web-platform-tests >>> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> >>> ?Yes >>> >>> Flag name >>> >>> Requires code in //chrome?False >>> >>> Tracking bug >>> https://bugs.chromium.org/p/chromium/issues/detail?id=1432798 >>> >>> Sample links >>> https://output.jsbin.com/hopejeb >>> >>> Estimated milestones >>> Shipping on desktop 117 >>> Shipping on Android 117 >>> Shipping on WebView 117 >>> >>> Anticipated spec changes >>> >>> Open questions about a feature may be a source of future web compat or >>> interop issues. Please list open issues (e.g. links to known github issues >>> in the project for the feature specification) whose resolution may >>> introduce web compat/interop risk (e.g., changing to naming or structure of >>> the API in a non-backward-compatible way). >>> None. >>> >>> Link to entry on the Chrome Platform Status >>> https://chromestatus.com/feature/5145771917180928 >>> >>> Links to previous Intent discussions >>> >>> This intent message was generated by Chrome Platform Status >>> <https://chromestatus.com/>. >>> >> -- > You received this message because you are subscribed to the Google Groups > "blink-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to blink-dev+unsubscr...@chromium.org. > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAHe_1dKPpadQmZeRkXjmXax73OTN7MjgG1hQxQ5rfjN8uTcEDg%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAHe_1dKPpadQmZeRkXjmXax73OTN7MjgG1hQxQ5rfjN8uTcEDg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- Thomas Steiner, PhD—Developer Relations Engineer (https://blog.tomayac.com, https://twitter.com/tomayac) Google Germany GmbH, ABC-Str. 19, 20354 Hamburg, Germany Geschäftsführer: Paul Manicle, Liana Sebastian Registergericht und -nummer: Hamburg, HRB 86891 ----- BEGIN PGP SIGNATURE ----- Version: GnuPG v2.3.4 (GNU/Linux) iFy0uwAntT0bE3xtRa5AfeCheCkthAtTh3reSabiGbl0ck0fjumBl3DCharaCTersAttH3b0ttom. hTtPs://xKcd.cOm/1181/ ----- END PGP SIGNATURE ----- -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALgRrLnrYnTKQ8gpKbp%2B4OztL%3D%3DxaaOyka_CoBo4YE_xN13Hug%40mail.gmail.com.
