- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 03 May 2017 16:51:46 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `Should flex-shrinking propagate back down the flex chain?`. <details><summary>The full IRC log of that discussion</summary> <dael> Topic: Should flex-shrinking propagate back down the flex chain?<br> <dael> Github topic: https://github.com/w3c/csswg-drafts/issues/1290<br> <dael> fantasai: I think this was fremy's. I haven't dug in much.<br> <dael> fremy: The issue is prob a chrome bug, but I waned to check<br> <dael> fremy:someone made a lot of good test cases. I agree witht he explination he gave. What he said makes sense. But if you're not ready to discuss I don't know if anyone is ready.<br> <dael> fremy: I can go ahead and file bugs and if it doesn't match spec the browsers will complain. Or we can wait. What do people feel.<br> <dael> astearns: I think you should file a bug. It's often the fastest way to determine if i t's a spec bug or can be fixed.<br> <dael> fremy: I was just trying to get feedback. Seems like it's prob a bug. If WG says file a bug I can.<br> <dael> astearns: Anyone from Chrome with an opinion?<br> <dael> TabAtkins: I can't look, so no opinion right now.<br> <dael> fremy: Summary: when you have flexbox in a flexbox and inner is auto. In all browsers except Chrome you size the flexbox normally. The fact t hat it's a flexbox in a flexbox affects size in Chromme.<br> <dael> fremy: I'll file a bug. We can discuss later if they come back. Sound good?<br> <dael> fantasai: Yep.<br> <dael> [trying to find source of background noise]<br> <dael> astearns: We'll file a bug and see how that goes.<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1290#issuecomment-298969914 using your GitHub account
Received on Wednesday, 3 May 2017 16:51:56 UTC