Re: [csswg-drafts] [css-text] How to handle leading ideographic space sequences ? (#4180)

The CSS Working Group just discussed `How to handle leading ideographic space sequences`, and agreed to the following:

* `RESOLVED: Trailing "other-separator spaces" will hang, accepting Florian's PR.`

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> Topic: How to handle leading ideographic space sequences<br>
&lt;TabAtkins> florian: this has evolved over time; they're a strange kind of space, like figure spaces, ideographic spaces, etc<br>
&lt;astearns> github: https://github.com/w3c/csswg-drafts/issues/4180<br>
&lt;TabAtkins> florian: These now have the treatment that they'r enot collapsible, that hasn't changed, bu tthey're discarded at the end of the line (assuming white-space:normal)<br>
&lt;TabAtkins> florian: Unfortunate consequence: if the line is *only* these spaces, they're not discarded for being at the beginning of the line, but they're also at the end of the line and need to be discarded. That leaves an empty line, which is weird.<br>
&lt;TabAtkins> florian: We coul dinsted hang them.<br>
&lt;TabAtkins> florian: Diff is you could still see them if you underline or background them.<br>
&lt;TabAtkins> florian: But from layout, it would be the same as an empty line.<br>
&lt;TabAtkins> florian: This was found by Igalia when implementing the spec as written, and it seemed weird to them.<br>
&lt;TabAtkins> florian: I think there's no real author preference between discarding and hanging. So since hanging is simpler for impls, would be preferable.<br>
&lt;TabAtkins> florian: I made a PR for this, I know fantasai is okay with this.<br>
&lt;TabAtkins> ???: Is there precedence fo rhaving that many hanging spaces?<br>
&lt;astearns> s/???/stantonm/<br>
&lt;TabAtkins> florian: Yes, we have some other situations like white-space:pre-wrap.<br>
&lt;TabAtkins> florian: There's an open issue for some variant situations, but...<br>
&lt;TabAtkins> stantonm: The inline border does seem strange.<br>
&lt;TabAtkins> stantonm: An inline with a border would project off the edge of the element.<br>
&lt;TabAtkins> florian: Like any overflowing content, es.<br>
&lt;TabAtkins> florian: Example: "&lt;span>a b       &lt;/span>". If the spaces can hang, these can stay on one line. If they can't and must overflow, instead you must break before b, then let that second line overflow anyway. So not hanging isn't avoiding overflow at all, just introducing extra linebreaks that shouldn't be necessary.<br>
&lt;TabAtkins> koji: Hanging would require changes to our whitespace code that we'd like to avoid if possible.<br>
&lt;TabAtkins> myles: there are like 5000 ways to make text look bad on the web already<br>
&lt;TabAtkins> stantonm: Is there a way to avoid this?<br>
&lt;TabAtkins> florian: Yes, text-underline-skip for example.<br>
&lt;TabAtkins> astearns: So proposed resolution is to accept the PR, which states that the spaces will hang.<br>
&lt;TabAtkins> astearns: Objections?<br>
&lt;TabAtkins> RESOLVED: Trailing "other-separator spaces" will hang, accepting Florian's PR.<br>
</details>


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

Received on Monday, 16 September 2019 08:11:29 UTC