W3C home > Mailing lists > Public > public-css-archive@w3.org > June 2019

Re: [csswg-drafts] [css-text] Clarify whether soft breaks exist at boundaries of an inline element with `word-break:break-all` (#3897)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 26 Jun 2019 16:49:34 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-505956757-1561567773-sysbot+gh@w3.org>
The CSS Working Group just discussed ``Clarify whether soft breaks exist at boundaries of an inline element with `word-break:break-all` ``.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: Clarify whether soft breaks exist at boundaries of an inline element with `word-break:break-all`<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/3897<br>
&lt;dael> fantasai: I don't know if we can resolve today. Issues is when you have a span of text with word-break:break-all on it and it's in a set of characters that would not break<br>
&lt;dael> fantasai: Clear that able to break between char, but what should happen at edges like first letter and previous letter. Jonathan kew posted an example. Browsers are inconsistent<br>
&lt;dael> fantasai: Spec says when breaking between 2 char you look at breaking prop on nearest common ancesistor. Jonathan argues how word-break is defined it reclassifies characters so that definition doesn't apply. Have behavior fall from reclassivication<br>
&lt;dael> fantasai: break-all is latin as cjk, keep-all is treat cjk as latin<br>
&lt;dael> fantasai: There's also some related properties. line-break which decides what rule sin effect. If we do character based we have asymmetric effects. Another thing is that one of the funidmental line breaking is white-space and that uses nears common ancestor def.<br>
&lt;dael> fantasai: Overview of considerations. This needs people to think about it and try to figure out best cases. There were use cases is favor of current spec. Nothing in favor of proposal. Use cases are particularly welcome<br>
&lt;dael> Rossen_: Thanks fantasai for summary. Issue has been kicked around for some time now. How to make it more actionable?<br>
&lt;dael> dbaron: To what extent do you feel like compat is an issue vs this is that impl haven't done well yet and you want to push toward impl of spec?<br>
&lt;dael> fantasai: I don't think there is a web compat issue. It's making sure impl of spec want to move forward in same direction<br>
&lt;dael> florian: I think it's inbetween. At first approx it doesn't seem impl follow spec, but they don't follow alternative or each other either. What they're closer to is difficult to say. You could make arguments either way. We should make everyone agree. I prefer the spec, but the alternative a 'b' in the last comment on the issue is sane but I like it less. Don't like 'c'<br>
&lt;fantasai> Summary of the state of the issue - https://github.com/w3c/csswg-drafts/issues/3897#issuecomment-505931859<br>
&lt;dael> Rossen_: Give a week or try for progress?<br>
&lt;dael> fantasai: I don't have anything to add. If others have something to add or want to think another week is good. Can try to ping i18n WG<br>
&lt;dael> florian: Maybe rule C out. Then action impl to look at a and b to see if one is harder<br>
&lt;dael> fantasai: Jonathan Kew advocated for c<br>
&lt;dael> florian: Oh, sorry.<br>
&lt;dael> Rossen_: fantasai can you ping i18n group?<br>
&lt;dael> Rossen_: Is b leading? No c? a is the spec. Seems people mostly gravitate to c<br>
&lt;dael> florian: I like spec as-is. Can't advocate alternative is bad. I would prefer not to change line-break.<br>
&lt;dael> Rossen_: a or c<br>
&lt;dael> florian: I'd object to c. But we don't have a clear winner<br>
&lt;dael> Rossen_: We'll ping people to chime in and look next week.<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3897#issuecomment-505956757 using your GitHub account
Received on Wednesday, 26 June 2019 16:49:37 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 19 October 2021 01:31:10 UTC