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

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

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 20 Feb 2019 17:15:41 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-465671641-1550682940-sysbot+gh@w3.org>
The CSS Working Group just discussed `When to/not to include preserved trailing spaces`, and agreed to the following:

* `RESOLVED: trailing spaces should be counted for max-content but not min-content`
* `RESOLVED: when preserved trailing spaces hang they do it using allow-end rather than force-end`

<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> fantasai: This was discussion with koji and xidorn with how trailing spaces handled for intrinisic sizing and alignment. xidorn suggested we consider then when counting for max content. For min content b/c trailing spaces don't create overflow or cause wrapping we shouldn't count them. So longest word, not longest work+space controls content<br>
&lt;dael> fantasai: Other suggestion was to define spaces hang according to allow-end rules. allow-end if it fits in the line it's not hanging. When you do right alignment it won't go outside. If it doesn't fit we allow it to fit on the line and in that case it's hanging<br>
&lt;dael> myles: Changing things about expansion opp. is something the web depends on. Do we have compat?<br>
&lt;dael> florian: We don'thave compat<br>
&lt;dael> myles: Meaning browsers do different things?<br>
&lt;dael> florian: Yes. safari does force-end and others do allow-end for alignment<br>
&lt;dael> myles: I don't think we have any philosophical desire so as long as no web compat problem we're willing to change<br>
&lt;dael> florian: fantasai your last comment in the issue can you clarify? I'm not sure where that's coming from<br>
&lt;dael> fantasai: xidorn confirmed my first comment and not second. I think I was trying to figure out...That question is about handling spaces after a forced break diff then soft break or if they're the same<br>
&lt;nigel> q+ to note https://github.com/w3c/csswg-drafts/issues/1997<br>
&lt;dael> fantasai: I think just treating the same is the plan unless someone thinks different<br>
&lt;dael> florian: I would think treat the same<br>
&lt;dael> fantasai: Obviously they're kind of different when doing [missed] content b/c there is no soft break<br>
&lt;fantasai> s/[missed]/max-content/<br>
&lt;dael> florian: For rest of the question I think in terms of taking into account for max content and not min content I initially thought we would ignore in both. If you think in terms of punctuation this proposal makes more sense. Including in max-content is right idea. For alignment I could go either way<br>
&lt;dael> fantasai: That's what I was thinking. spaces then text then spaces. If we say hang in general and you wrap halfway throught he text you'd see the beginning spaces but not the end. If you right align we end up hanging them<br>
&lt;dael> fantasai: Gonna depend on how they happen to fit. I think proposed behavior is fine<br>
&lt;dael> florian: Makes sense. Good argument<br>
&lt;dael> astearns: nigel had a point but he's having difficulty being heard<br>
&lt;dael> fantasai: If asking about issue #1997 that's about if inline elements interrupt whitespace trimming. whitespace is trimmed when collapsible, but this is when it's not collapsable so it's not really related<br>
&lt;dael> astearns: nigel can you indicate on IRC if that makes sense?<br>
&lt;nigel> okay, I was just referencing that other issue because it seemed relevant<br>
&lt;dael> florian: I am in supprot of proposal. Tests need to be updated but I will do so<br>
&lt;dael> astearns: trailing spaces should be counted for max-content but not min-content<br>
&lt;nigel> and space allocation at the ends of lines is a big deal for e.g. captions.<br>
&lt;dael> astearns: Objections?<br>
&lt;dael> RESOLVED: trailing spaces should be counted for max-content but not min-content<br>
&lt;dbaron> this is all just *preserved* trailing spaces, right?<br>
&lt;dael> astearns: What is next thing to resolve?<br>
&lt;florian> dbaron, yes<br>
&lt;dael> fantasai: when spaces hang they hand using allow-end behavior rather than force-end<br>
&lt;dael> astearns: dbaron has a question on previous and that is correct as far as I understand<br>
&lt;dael> fantasai: Yes.<br>
&lt;nigel> q-<br>
&lt;dael> astearns: Next is when preserved trailing spaces hang they do it using allow-end rather than force-end<br>
&lt;dael> RESOLVED: when preserved trailing spaces hang they do it using allow-end rather than force-end<br>
&lt;dael> fantasai: Think that's all on this issue<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3440#issuecomment-465671641 using your GitHub account
Received on Wednesday, 20 February 2019 17:15:42 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:44 UTC