Re: [csswg-drafts] [css-text-3] overflow-wrap: break-spaces can effect behavior even when there are previous breaking opportunities in the line

The Working Group just discussed `overflow-wrap: break-spaces can effect behavior even when there are previous breaking opportunities in the line`, and agreed to the following resolutions:

* `RESOLVED: Simplify the definition of break-spaces as in this commit: https://github.com/w3c/csswg-drafts/commit/1a6a12db7f8b431fe4646c634aa823105208f1d4`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: overflow-wrap: break-spaces can effect behavior even when there are previous breaking opportunities in the line<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/2003#issuecomment-370652901<br>
&lt;dael> florian: myles noticed a complication in a corner case of the handling of break space. Initially intentionally introduced, but it is a complication. Since line-break-anywhere exists this brings nothing to the platform. All varients remain possible.<br>
&lt;dael> myles: Background, we are interested in using icu breaking iterators. There's a bunch of modifiers for breaking including overflow-wrap which should only kick in if a breaking oportunity wasn't in the line until the end.<br>
&lt;dael> myles: Corner case is where we couldn't look at all properties and create icu breaking iterator because breaking opportunities depending on earlier in the line. It would be great if this corner case could be removed.<br>
&lt;dael> myles: I believe the commit fantasai maded satisfies that constraint so it's okay now.<br>
&lt;dael> astearns: Concerns with this simplification?<br>
&lt;dael> Rossen_: Trying to wrap my head around what it means for impl that impl the corner case.<br>
&lt;dael> florian:  no one impl yet.<br>
&lt;dael> Rossen_: I think not in a shipping form.<br>
&lt;dael> myles: As I understand if I impl what was in there before I need special handling and an if statement. I think after there's no if or special handling. I don't know how the Edge impl works but Iwould imagine it would be simplier.<br>
&lt;dael> florian: There was also a slight error in the wording for the spec. [reads]  If we remove the normative requirement there's independance where there was interference before the change.<br>
&lt;dael> florian: For the details of what and why we're need a whiteboard.<br>
&lt;dael> Rossen_: If we can attach the JS to exemplify that would be great.<br>
&lt;dael> myles: I couldn't fiddle but I did mockups in pngs insided the thread.<br>
&lt;dael> myles: Proposed resolution is to accept fantasai's commit.<br>
&lt;dael> Rossen_: I did review. I won't object. I'm just trying to work through ramifications.<br>
&lt;dael> astearns: So Rossen_ are you okay to resolve now or do you want time?<br>
&lt;dael> Rossen_: We can resolve now. I will pay witht he behavior and try to come up with the test cases myles was trying to examplify. I don't think i t'll be a problem.<br>
&lt;dael> astearns: Obj to simplify defintion of break spaces?<br>
&lt;dael> Rossen_: What is the technical version of that resolution?<br>
&lt;dael> astearns: WE have the commit. Simplify the definition of break-spaces as in this commit.<br>
&lt;florian> url to the commit: https://github.com/w3c/csswg-drafts/commit/1a6a12db7f8b431fe4646c634aa823105208f1d4<br>
&lt;dael> Rossen_: great<br>
&lt;dael> RESOLVED: Simplify the definition of break-spaces as in this commit: https://github.com/w3c/csswg-drafts/commit/1a6a12db7f8b431fe4646c634aa823105208f1d4<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2003#issuecomment-375005044 using your GitHub account

Received on Wednesday, 21 March 2018 16:25:59 UTC