-
Notifications
You must be signed in to change notification settings - Fork 747
[css-text-4] Replace word-boundary-detection: auto()
with word-break: phrase
#8974
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this 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:
This looks great to me, thank you so much. Would you try to get a resolution at WG? |
I added Agenda+ to #7193. |
word-boundary-detection: auto()
with word-break: phrase
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=]. |
There was a problem hiding this comment.
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.)
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. |
There was a problem hiding this comment.
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.
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=]. |
There was a problem hiding this comment.
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).
User agents that do not support the [=User Origin=] | ||
should use the [=User-Agent Origin=] instead. |
There was a problem hiding this comment.
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.
Addresses @fatnasai's feedback at: w3c#8974 and the WG resolutions at: w3c#7193 (comment)
addressed by #9242 |
From #7193, this replaces
word-boundary-detection: auto()
withword-break: phrase
.