- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Tue, 27 Jan 2026 22:26:57 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-overflow-4] where to clamp when a float pushes a whole line down`, and agreed to the following: * `RESOLVED: Clamp at the bottom of the last line or in-flow block-level box before the clamp point` <details><summary>The full IRC log of that discussion</summary> <emilio> florian: several things we're not discussing... not talking about slicing floats and so on<br> <emilio> ... if you have a reasonably narrow float, next to it there are lines, and that's fine<br> <emilio> ... we're looking at whether your float is large enough there's no line next to it<br> <emilio> ... in the example we clamp after 5 lines<br> <emilio> ... and a float is after 4<br> <emilio> ... we're clamping five line-heights, clamp point is right after the float but there's no line there<br> <emilio> ... so we can't clamp after line 4 because line 5 is not next to it<br> <emilio> ... so we'd need to clamp between 3 and 4<br> <emilio> ... which is sillly<br> <emilio> ... so let's not do that?<br> <emilio> fantasai: isn't it similar to clamping with a margin?<br> <emilio> ... imagine instead of a float we have a margin<br> <emilio> florian: right now it's undefined if the break point is not between lines<br> <andreubotella> q+<br> <emilio> ... the two lines are not adjacent<br> <emilio> fantasai: you'd clamp between 4 and 5 and define the clamp point is at the bottom of line 4<br> <astearns> ack andreubotella<br> <emilio> florian: I think what you're saying let's us amend the resolution to skip floats _and_ absposes<br> <astearns> qq+ iank_<br> <emilio> andreubotella: if we have two line boxes separated by a float<br> <emilio> ... do we consider them siblings?<br> <emilio> fantasai: yes<br> <emilio> andreubotella: then the current spec would be right<br> <emilio> ... in this specific case<br> <emilio> ... if we have a float between block siblings then that's different<br> <emilio> fantasai: I think the lines are siblings, I don't think we define a line box tree or something<br> <emilio> ... line boxes are their own tree<br> <emilio> q+<br> <emilio> ... so they have a concept of containment that's independent of the box tree<br> <emilio> andreubotella: I think those should count as consecutive?<br> <emilio> ... if a float pushes it down is it still consecutive?<br> <emilio> fantasai: florian: yes<br> <emilio> andreubotella: we should have that in the spec<br> <emilio> florian: there's a remaining subtlety<br> <emilio> ... they are not adjacent<br> <emilio> ... so where do we put the ellipsis?<br> <emilio> fantasai: we need to define that<br> <emilio> emilio: bottom of the last line before the clamp point?<br> <emilio> fantasai: yes<br> <florian> yes<br> <florian> q?<br> <emilio> andreubotella: there's another issue which is if we're clamping between two in-flow block-level sibling boxes<br> <emilio> ... I assume that means we already don't count floats<br> <emilio> ... so we'd clamp before the float<br> <emilio> q-<br> <emilio> ack iank_<br> <Zakim> iank_, you wanted to react to andreubotella<br> <astearns> ack iank_<br> <emilio> iank_: I think I'm fine, but this is only about line-clamp: auto case right?<br> <astearns> ack dbaron<br> <Zakim> dbaron, you wanted to mention clear<br> <emilio> ... the number case is also well defined?<br> <emilio> florian: yes<br> <emilio> dbaron: should we think about clearance?<br> <florian> q+<br> <emilio> ... might be worth thinking about whether `clear` (which you can only exercise within a nested block) behaves similarly here<br> <astearns> ack fantasai<br> <emilio> fantasai: can also specify it on `<br>`<br> <emilio> fantasai: the other answer is that the clamp point is at the height<br> <emilio> andreubotella: then it's only about where you clamp<br> <emilio> fantasai: if you clamp at 5lh that's what the author said, otherwise you clamp at 4lh<br> <emilio> florian: but there's nothing in between 4lh and 5lh<br> <emilio> fantasai: there's the float<br> <fantasai> emilio: The float would overflow no matter what, question is whether it overflows totally or partially<br> <fantasai> fantasai: Also question of how much it overflows<br> <fantasai> emilio: You're positioning the ellipsis at the top (at 4lh) then shouldn't you clamp at 4lh?<br> <fantasai> florian: If you ask for a height-based lamp point, you're not guaranteed exactly that much content<br> <fantasai> florian: you'll always get entire things<br> <fantasai> fantasai: what if I asked for height: 5lh?<br> <emilio> florian: that'd behave differently<br> <emilio> emilio: it clamps the auto height<br> <astearns> ack florian<br> <emilio> emilio: if you want the behavior of getting 5lh you can use height: 5lh<br> <emilio> ... then you get the behavior you want<br> <emilio> florian: re. clearance I suspect we get similar behavior, it doesn't matter whether the content gets push down due to clearance<br> <emilio> ... or due to lack of space<br> <fantasai> emilio: We clamp at the bottom of the last line that is before the clamp point.<br> <fantasai> andreubotella: last line or block-level box<br> <fantasai> emilio: floats..<br> <emilio> RESOLVED: Clamp at the bottom of the last line or in-flow block-level box before the clamp point<br> <emilio> emilio: which box, margin box?<br> <emilio> florian: should be defined but if it's not new issue<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12817#issuecomment-3807831353 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 27 January 2026 22:26:58 UTC