Re: [w3ctag/design-reviews] text-wrap: pretty (Issue #864)

Hi there,

We looked at this in the plenary on Wednesday.

In general, we recommend explainers to be in Markdown, and are [in the process](https://github.com/w3ctag/tag.w3.org/pull/39) of merging guidance to that effect in the Explainer Explainer.
Some more reasons for this in https://github.com/w3ctag/tag.w3.org/issues/30#issuecomment-1621965117 .

We were also a little confused about the name, since it seems that this feature is about controlling orphan words and `pretty` is very generic, which is why I reached out to @fantasai for clarification. If the intent of the spec is to have many varied heuristics into making text wrapping more aesthetically pleasing, I am a little worried about whether the current implementation can evolve into that. I can easily see authors starting to use it as a property to control orphans, and before we know it, we can’t change it due to web compat.
The way [authors are already evangelizing it](https://twitter.com/chriscoyier/status/1681407724993798144) confirms these fears so far.

If all this property does is prevent orphan words, I wonder if a property to control exactly that would be preferable, possibly as a longhand of `text-wrap` (`text-wrap-orphans`?). This could also give authors more control, and would be far more discoverable.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/864#issuecomment-1646646652
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/864/1646646652@github.com>