E53D [css-text-4] Replace `word-boundary-detection: auto()` with `word-break: phrase` by litherum · Pull Request #8974 · w3c/csswg-drafts · GitHub
[go: up one dir, main page]

Skip to content

Conversation

litherum
Copy link
Contributor
@litherum litherum commented Jun 16, 2023

From #7193, this replaces word-boundary-detection: auto() with word-break: phrase.

Copy link
Contributor
@kojiishi kojiishi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the PR, this looks great! Some comments:

@kojiishi
Copy link
Contributor

This looks great to me, thank you so much. Would you try to get a resolution at WG?

@litherum
Copy link
Contributor Author

This looks great to me, thank you so much. Would you try to get a resolution at WG?

I added Agenda+ to #7193.

@litherum litherum changed the title [css-text-4] Add word-break:auto [css-text-4] Add word-break:phrase Jun 23, 2023
@litherum litherum changed the title [css-text-4] Add word-break:phrase [css-text-4] Replace word-boundary-detection: auto() with word-break: phrase Jun 23, 2023
Comment on lines +4487 to +4491
Authors who prepare their content in this manner
should not rely on the initial value, and
should explicitly specify ''word-break'' on the relevant parts of the content,
in order to override a potential ''word-break: auto''
in the [=User Origin=] or [=User-Agent Origin=].
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe this is no longer relevant. (The previous model relied on specifying word-break: keep-all in order to work.)

Comment on lines +4482 to +4485
Manual analysis of the content can be more reliable than UA heuristics.
For best results, authors who can perform this analysis are encouraged to markup their documents
using <{wbr}> or U+200B
to exhaustively indicate word boundaries.
Copy link
Collaborator
@fantasai fantasai Jun 30, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should probably add that UAs should respect such WBRs as more authoritative than their automatic detection, similar to soft hyphens.

Comment on lines +4467 to +4472
User agents may activate
language-specific content analysis
in response to user preferences.
User agents with this behavior must do this
by setting the [=declared value=] of 'word-break' to ''word-break/phrase''
in the [=User Origin=].
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This bit should go into a separate section about accessibility tweaks that the UA can provide, not here in the core definition (where it interrupts understanding the property).

Comment on lines +4473 to +4474
User agents that do not support the [=User Origin=]
should use the [=User-Agent Origin=] instead.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we need to say anything about what happens when a UA is non-conformant to css-cascade.

kojiishi added a commit to kojiishi/csswg-drafts that referenced this pull request Aug 22, 2023
Addresses @fatnasai's feedback at:
w3c#8974

and the WG resolutions at:
w3c#7193 (comment)
@frivoal
Copy link
Collaborator
frivoal commented Sep 1, 2023

addressed by #9242

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants
0