- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Jun 2024 13:52:06 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-overflow-4] Line-clamp and IFC`, and agreed to the following: * `RESOLVED: line-clamp establishes an independent formatting context` <details><summary>The full IRC log of that discussion</summary> <fantasai> florian: This and the next issue are similar context<br> <fantasai> florian: for line-clamp we currently have a spec that uses something called 'continue: discard' which invokes fragmentation<br> <fantasai> florian: some discussion about an alternative approach that relies on visibility-hidden type thing instead<br> <fantasai> florian: awhile back we resolved to spec both and figure it out<br> <fantasai> florian: So Andreu has been prototyping both<br> <fantasai> florian: and we are developing spec for both<br> <fantasai> florian: We're looking at cases where the effects are accidentally differnet rather than intentionally<br> <fantasai> florian: Trying to harmonize them where possible<br> <fantasai> florian: this is one o them.<br> <fantasai> florian: When we initially drafted line-clamp using continue: discard<br> <fantasai> florian: we decided it shouldn't automatically become an independent formatting context<br> <fantasai> florian: it seemed possible to do so; and authors could always opt in using e.g. `display: flow-root`<br> <fantasai> florian: Driven by making it more nice, not by specific use cases<br> <fantasai> florian: Andreu found it was significantly simpler to implement if it was an independent formatting context<br> <fantasai> florian: so proposal is to do that instead<br> <fantasai> andreubotella: -webkit-line-clamp creates an independent formatting context due to creating a flexbox<br> <fantasai> andreubotella: For continue:discard there's also an aspect of complexity<br> <fantasai> andreubotella: it is assumed that every fragmentation container is an IFC<br> <fantasai> andreubotella: not clear what happens to floats if you have them break in the middle of a fragmentation container that isn't an IFC<br> <fantasai> andreubotella: Perhaps fragmentation spec that maybe all fragmentation containers should be IFC<br> <florian> s/making it more nice/making it more generic<br> <fantasai> andreubotella: When implementing it, it was clear that assuming IFC was so much easier that I didn't even attempt to not<br> <fantasai> andreubotella: For continue:collapse the considerations are different<br> <fantasai> andreubotella: I visualized that everything after clamp point should work like there's no content in the tree beyond the clamp point<br> <fantasai> andreubotella: That means clamped floats should not affect the outside<br> <fantasai> andreubotella: but what happens within the clamped function? should those floats affect each other?<br> <fantasai> andreubotella: in the end it was a lot easier to just not have that interaction with the outside of the line-clamp container by making it an IFC also<br> <emilio> q+<br> <fantasai> andreubotella: It could still be possible to implement, but would be significantly more complex to implement<br> <fantasai> andreubotella: and as Florian said, there's no significant use case for not making IFC<br> <astearns> ack emilio<br> <fantasai> iank_: It'll also be a lot easier for developers to transition to the new line-clamp because existing prefixed version establishes IFC<br> <fantasai> emilio: Agree<br> <astearns> ack dbaron<br> <fantasai> dbaron: The argument that you made at the end, that we don't want floats clipped by line-clamp to influence floats outside, seems like a good theoretical argument for why this is a sensible behavior that fits with everything else<br> <fantasai> dbaron: so I'm also in favor<br> <fantasai> astearns: Proposed resolution that line-clamp establishes an independent formatting context<br> <fantasai> emilio: When applied to blocks it creates an IFC<br> <dbaron> a BFC<br> <dbaron> (block formatting context)<br> <fantasai> RESOLVED: line-clamp establishes an independent formatting context<br> <dbaron> (I had just asked about whether we were talking about a block formatting context.)<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10323#issuecomment-2163068422 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 12 June 2024 13:52:07 UTC