- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Thu, 03 Mar 2022 00:42:58 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-flexbox] Multi-line column flexbox fragmentation`, and agreed to the following: * `RESOLVED: Treat items as not monolithic` * `RESOLVED: update fragmentation rules to flexbox to handle multiline independently` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: [css-flexbox] Multi-line column flexbox fragmentation<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/6855<br> <dael> alisonmaher: This issue is how to handle frag for multi line column. A couple questions<br> <dael> alisonmaher: First is around the spec rec to treat items as monolithic. Curious reasona nd if we should remove b/c otherwise items in a single line could frag differently than a 1 line multi line<br> <TabAtkins> q+<br> <dael> alisonmaher: Also, each element has it's own stack. Implies multi-line column flex has it's own context except items are monolithic. Doesn't make sense. If we frag independantly the result would be closer to unfragmented. Firefox doesn't match for either of these<br> <dael> alisonmaher: Prop is update spec to match FF for frag multiline column<br> <dael> alisonmaher: May have to reconsider break-before and -after<br> <dael> alisonmaher: Curious about reasons to keep spec text as is<br> <Rossen_> ack TabAtkins<br> <dael> TabAtkins: First, alisonmaher , this entire chapter was a best guess set up and we're happy to change to match impl or good results.<br> <dael> TabAtkins: What you're saying makes sense. Pending more detailed review as I write this seems plausable<br> <Rossen_> ack fantasai<br> <dael> fantasai: What TabAtkins said, chapter was a best guess. Multiline column felxbox was the weirdest. Written the way it was b/c not sure what you're suggesting is possible. If it is possible to shuffle across page break, it makes more sense.<br> <dael> fantasai: As to if we should make any changes to this, we should try and match both good behavior and implementations. I think these changes make sense<br> <Rossen_> q?<br> <dael> Rossen_: Other opinions? fwiw I remember some reasoning behind monolithic items it was b/c simplier and we were waiting for an implementation and here we are<br> <dael> Rossen_: alisonmaher can you summerize<br> <dael> alisonmaher: Update flexbox spec to frag multiline columns independantly and make items not monolithic<br> <dael> robObj to not monolithic?<br> <dael> RESOLVED: Treat items as not monolithic<br> <dael> Rossen_: Obj to update fragmenetation rules to flexbox to handle multiline independent<br> <dael> RESOLVED: update fragmentation rules to flexbox to handle multiline independently<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6855#issuecomment-1057547095 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 3 March 2022 00:43:00 UTC