-
Notifications
You must be signed in to change notification settings - Fork 711
[css-text-3] replaced elements and atomic inlines with non default line-break #4755
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
…ne-break This is a follow up to w3c#4576 This makes replaced elements and atomic inlines with non default line-break behave the same as characters with line-breaking class ID. This gives the expected behavior for images used as “gaiji” and as emoji. This cannot be the default behavior for compat reasons, but having it as an opt-in based on the rarely used line-break property should be safe.
I would like us to use any other properties than The effect of using incorrect values of html { line-break: strict; } but authors will not notice it has undesired side effects until they test it with CJK content. This can lead to a situation where global sites to use undesired typography only for CJK content. |
@kojiishi The initial value of |
Closed as the resolution in #4949 (comment) decided on a different approach. |
This is a follow up to #4576
This makes replaced elements and atomic inlines with non default values for
line-break
behave the same as characters with line-breaking class ID for line breaking purposes. This gives the expected behavior for images used as “gaiji” and as emoji.This cannot be the default behavior for compat reasons, but having it as an opt-in based on the rarely used line-break property should be safe, and opens up for further tweaking of the line breaking behavior via the usual set of properties.