Re: [csswg-drafts] [css-overflow-3] Define the behavior of overly long block ellipsis strings

The CSS Working Group just discussed `long block ellipsis strings`, and agreed to the following:

* `RESOLVED: ellipsis string is non breakable`

<details><summary>The full IRC log of that discussion</summary>
&lt;astearns> topic: long block ellipsis strings<br>
&lt;astearns> github: https://github.com/w3c/csswg-drafts/issues/3213<br>
&lt;eae> florian: I have a paragraph with lorem ipsum, the width is very narrow, we line clamp it and have ellipsis. What should happen when the ellipsis itself is longer than the line. One option is to consider the ellipsis  unbreakable and have it stick out.<br>
&lt;eae> florian: The alternative, it is wrappable, and wraps up into the previous line.<br>
&lt;eae> myles__: How does the implemention know which line to start on?<br>
&lt;eae> florian: I feel it is an edge cases that will rarely happen, first option seems a lot easier.<br>
&lt;eae> TabAtkins: The wrapping behavior doesn't  solve the problem of it being too wide<br>
&lt;eae> florian: Do we need to solve the porblem where it could wrap. I suggest we don't.<br>
&lt;eae> florian: Third way is leave it undefined, don't like it.<br>
&lt;eae> TabAtkins: Should be similar to have we do ellipsis now, remove enough characters until it fits<br>
&lt;eae> fantasai: This seems easier, don't have to care about the many ways of doing wrapping.<br>
&lt;eae> fantasai: I think the proposed resolution is to go with the first option<br>
&lt;eae> Proposed resolution: ellipsis is treated as unwrappable and will extend outside<br>
&lt;eae> TabAtkins: It's not great to overflow but at least you can see it.<br>
&lt;eae> astearns: Objections?<br>
&lt;eae> RESOLVED: ellipsis string is non breakable<br>
</details>


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

Received on Monday, 22 October 2018 18:42:18 UTC