The CSS `word-break: auto-phrase` property

[kojiishi]

Hello TAG!

I'm requesting a TAG review of the CSS word-break: auto-phrase property..

This feature enables keeping natural phrases (of multiple words) together when line breaking.

• Explainer¹ (minimally containing user needs and example code): url
• Specification URL: url
• Tests: wpt folder(s)
• User research: url to public summary/results of research
• Security and Privacy self-review²: url
• GitHub repo (if you prefer feedback filed there): url
• Primary contacts (and their relationship to the specification):
  • @kojiishi (implementer), @bfgeek (implementer), @fantasai (spec editor), @frivoal (spec editor), @astearns (csswg char), @atanassov (csswg char)
• Organization(s)/project(s) driving the specification: @fantasai, @frivoal
• Key pieces of existing multi-stakeholder review or discussion of this specification: https://github.com/w3c/csswg-drafts/issues/7193
• External status/issue trackers for this specification (publicly visible, e.g. Chrome Status): https://chromestatus.com/feature/5133892532568064

Further details:

• [x] I have reviewed the TAG's Web Platform Design Principles
• Relevant time constraints or deadlines: Implementation complete.
• The group where the work on this specification is currently being done: CSSWG
• The group where standardization of this work is intended to be done (if current group is a community group or other incubation venue): CSSWG
• Major unresolved issues with or opposition to this specification: None
• This work is being funded by: Blink implementation is being done by Google.

We'd prefer the TAG provide feedback as (please delete all but the desired option): 💬 leave review feedback as a comment in this issue and @-notify [@kojiishi (implementer), @bfgeek (implementer), @fantasai (spec editor), @frivoal (spec editor)]

[rhiaro]

Hi @kojiishi please could you update your request with the rest of the template filled in?

[kojiishi]

Hi @rhiaro, sorry I missed some fields to fill in. Done.

[torgo]

Hi @kojiishi we really need an explainer in order to do a review. Also can you please clarify at what stage this is in in the CSS working group? Is this still under discussion or has this reached consensus?

[kojiishi]

Updated.

[frivoal]

Can you please clarify at what stage this is in in the CSS working group?

Quite settled. We might have to address follow up issues if raised, but the core of the discussion has settled, and the spec is where we expect it to be for this feature.

Explainer

In addition to the document shared by Koji, appendix H in the spec, as well as example 22 do give some examples and some high level description of what this is.

[rhiaro]

Thanks @kojiishi. We see no architectural concerns, and are happy to close this review.

We would like to note that you haven't filled out the privacy and security questionnaire, but have linked to the security and privacy sections in your spec, the first of which contains nothing, and the second of which contains one sentence:

This specification leaks the user’s installed hyphenation and line-breaking dictionaries.

We were wondering if you could expand on the risks here, and if there are mitigations for this that could/should be elaborated on in this section, or if it's not really a concern, then why not?