Re: [csswg-drafts] [css-text][css-sizing] When to/not to include preserved trailing spaces (#3440)

The CSS Working Group just discussed `When to/not to include preserved trailing spaces`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: When to/not to include preserved trailing spaces<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/3440<br>
&lt;dael> florian: Before concluded whitespaces at the end of a line for whitespace pre-wrap force hang.But spaces before forced break wouldn't hang.<br>
&lt;dael> florian: Based on issue fantasai prop in order to make them count to max content, but definition of hanging doesn't say if they count or not.<br>
&lt;dael> florian: THen again spaces before a forced break also shoudln't count to min content<br>
&lt;dael> florian: If you look at interop browsers don't treat spaces before a forced break differently<br>
&lt;dael> florian: I think we shoudls ay they hang regardless of forced or soft wrap, but say they count toward max-content size.<br>
&lt;dael> florian: Also clarify if hanging punct. counts or not. Implied maybe, but hanging on intrinsic size isn't explicit<br>
&lt;dael> fantasai: [reads spec]<br>
&lt;fantasai> https://www.w3.org/TR/css-text-3/#hang<br>
&lt;dael> florian: Doesn't say for intrinsic. For min talked explicitly, but for max it's fuzzy. In punct case...it's saying a bunch of things and you can figure out what they prob mean but it doesn't say it explicitly. Esp. given tests aren't clear there's interop so clarifying is good<br>
&lt;dael> florian: I rpoposed we clarify toward don't count regardless of it's min or max. Space we don't count for min and do for max. I think that matches rough interop<br>
&lt;dael> fantasai: If we include it in max content size but then subsiquently align to the right the max content no longer fits the content. This is why we want to be consistent if it's counter for alignment max content and justification. Need same answer or otherwise weird<br>
&lt;dael> florian: Also quite weird with non-intrinisic size. You've got whitespace at the end of lots of lines. All except last align to the right. That's also weird.<br>
&lt;dael> fantasai: Yeeah. But in other cases you're wrapping. Whitespace at wrap you expect to disappear. Whitespace before a break you didn't have to put it there.<br>
&lt;dael> fantasai: If behavior makes more or less sense dependson if content is wrapping or not. Nice if right/left/center align is consistent and encased in max-content<br>
&lt;dael> fantasai: No great answer here. Having max-content and align have different answers doesn't make sense<br>
&lt;fantasai> s/answers/answers on a single line/<br>
&lt;dael> florian: If koji's test is still accurate everyone includes spaces for max and most but not all include for right align. Webkit and blink don't include for justification so they do that differently then alignment<br>
&lt;dael> florian: Last time around we resolved to align with WK and Blink for justificaiton and apply that to right align so never include the spaces.<br>
&lt;dael> florian: It's weird anyway. I have tests to match previous, I just think it's weird.<br>
&lt;dael> Rossen_: We're overtime<br>
&lt;dael> Rossen_: I don't feel we're ready to resolve.<br>
&lt;dael> florian: I think we forced last time and that's part of problem<br>
&lt;dael> Rossen_: Table discussion back to github. For those interested, continue there and we'llr esume next week<br>
&lt;dael> florian: Please look, what we have is well defined, but I'm not sure it's good.<br>
</details>


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

Received on Thursday, 2 May 2019 00:03:30 UTC