#822: text-wrap: balance
Discussions
2023-03-13
Lea: process should be if there's no objection in channel - rather... People should be more active on slack...
Lea: things should not be accepted and closed summarilly without people looking at it.
Lea: a lot of excitement in the open community about this.
we leave to async process to close
Hi - just a quick request hopefully - we noticed that the explainer is a google doc, not in a markdown next to the spec. There doesn't appear to be an answer to the security & privacy questionnaire. The chrome status also doesn't reflect the reality as shown by the web platform tests info. We recognise that this is already in the spec and there's significant developer support but can you please update the request info so we can progress?
Dan: leaves comment
2023-03-20
Tess: I think we can close it. They've thought about the issue.. Algorithmic complexity... 10 or more lines...
Peter: just for screen?
Tess: in most browsers the user experience of print styles being different from screen styles confuses people.. it's worth raising...
Rossen: what's the printing point?
Tess: if you're printing the UA can...
agreed to close with satisified
OpenedFeb 28, 2023
Hello TAG!
I'm requesting a TAG review of the
text-wrap: balance
CSS property.This feature adjusts line breaking to balance the length of each line box in a block, for better readability and to prevent typographic widows. This feature is often used in headlines.
There are several JavaScript libraries to achieve this effect, such as NYTimes text balancer, React Wrap Balancer, or Adobe Balance Text.
Jen's tweet has a sample image, and it got a lot of positive responses from web developers.
Further details:
💬 leave review feedback as a comment in this issue and @-notify [github usernames]