Re: [csswg-drafts] Allowing (or not) alternate ellipsis behavior for block-overflow

The CSS Working Group just discussed `Allowing (or not) alternate ellipsis behavior for block-overflow`, and agreed to the following:

* `RESOLVED: Edit in Mats proposed solution from issue 2905.`

<details><summary>The full IRC log of that discussion</summary>
&lt;astearns> topic: Allowing (or not) alternate ellipsis behavior for block-overflow<br>
&lt;astearns> github: https://github.com/w3c/csswg-drafts/issues/2905<br>
&lt;eae> florian: A part of the spec that says it's undefined. Gives two options. YOu layout your text and insert your ellipsis and remove content up until it fitst. Properly inserted text and you redo layout.<br>
&lt;eae> florian: Then there is a may. If you are time-pressed there is an easy way, inserted the same way as text overflow. Does not affect layout, paint time effect./<br>
&lt;eae> florian: Not great that spec allows two different behaviors.<br>
&lt;eae> florian: There is a next level of spec that allows other behaviors. Should we remove the may and make the correct behavior mandatory.<br>
&lt;eae> florian: Someone suggested that we might want to do an intermediate. You do the right thing when removing content but the insertion of the ellipsis is allowed to be a paint time effect.<br>
&lt;eae> astearns: If the ellipsis removes the entire last line would that change the line-height?<br>
&lt;eae> florian: Would retain a strut to preserve line height.<br>
&lt;eae> heycam: What happens with interactions like bidi reordering?<br>
&lt;eae> fantasai: I would imagine that the ellipsis would be bidi isolate<br>
&lt;eae> heycam: Also other interactions?<br>
&lt;eae> fantasai: If the ellipsis is rendered in a font that is taller than the line it is rendered onto the line would be taller which could cause that line to be droped<br>
&lt;eae> florian: That problem doesn't necessarily need solving.<br>
&lt;eae> heycam: Removal of glyphs, back up to however many glyphs needs to be dropped.<br>
&lt;eae> florian: How far you're allowed to back up, if you have hyphenation or in japanese where you can break anywhere. Line wrapping opportunities.<br>
&lt;eae> myles__: So not glyph based at all?<br>
&lt;eae> florian: Not half glyphs, at least one glyph, often more<br>
&lt;eae> astearns: proposal as I understand, remove content as required to ensure enough space, leave a strut as needed, and then add ellipsis at paint time?<br>
&lt;eae> heycam: Logically trim of pieces of the DOM that won't be rendered?<br>
&lt;eae> florian: You don't drop the line wherever, reuse the same logic as used for line breaking for fragmentation. Consider the last line to be shorter to allow for the ellipsis.<br>
&lt;eae> astearns: Would this be better for screenreaders?<br>
&lt;eae> florian: That is one case.<br>
&lt;eae> astearns: Any concerns about removing content and then paining ellipsis?<br>
&lt;eae> astearns: Mats saied:<br>
&lt;eae> flow the block as if block-overflow doesn't exist<br>
&lt;eae> if it caused overflow, then shorten the available space to accommodate the size of an ellipsis and flow the last line again<br>
&lt;eae> repeat 2 until there is no additional overflow or the line is empty<br>
&lt;eae> during painting, render an ellipsis in the reserved space in the last line (same as a text-overflow ellipsis)<br>
&lt;eae> florian: Repeat is potentially needed to reflow. Proper layout for removal.<br>
&lt;eae> astearns: One additional thing: If the line is empty, preserve the height.<br>
&lt;eae> astearns: Any concerns?<br>
&lt;eae> heycam: I don't like the searching and dropping bits to adjust the line height.<br>
&lt;eae> florian: tempted to say yes, haven't thought about it in detail.<br>
&lt;eae> florian: Would look a bit odd if you had a japanese word with ruby that has been dropped but still have a large gap above the line<br>
&lt;eae> florian: I do think we should make it narrower, don't want large gaps. Not common but would look really bad.<br>
&lt;eae> florian: Not taking to CR anytime soon, edit it in and then revisit once speced?<br>
&lt;eae> RESOLVED: Edit in Mats proposed solution from issue 2905.<br>
&lt;timeless> s/YOu/You/<br>
</details>


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

Received on Monday, 22 October 2018 18:47:09 UTC