- From: Alex Mogilevsky <alexmog@microsoft.com>
- Date: Wed, 6 Mar 2013 12:17:24 +0000
- To: Tab Atkins Jr. <jackalmage@gmail.com>, Ojan Vafai <ojan@chromium.org>
- CC: Boris Zbarsky <bzbarsky@mit.edu>, www-style list <www-style@w3.org>, Daniel Holbert <dholbert@mozilla.com>, Rossen Atanassov <Rossen.Atanassov@microsoft.com>
± From: Tab Atkins Jr. [mailto:jackalmage@gmail.com] ± Sent: Tuesday, March 5, 2013 7:04 PM ± ± On Tue, Mar 5, 2013 at 6:15 PM, Ojan Vafai <ojan@chromium.org> wrote: ± > There doesn't seem to be any opposition to this. Can we change the ± > spec soon? I'd really like to make this change ASAP. We keep hearing ± > reports of people hitting this and getting confused. ± ± My only hesitation is that MS people haven't commented yet. I'm explicitly ± pinging them in the CC list. You want to hear from Rossen, as I am no longer in the loop for usability concerns that you are describing. I did advocate adding 'auto' as default min-width though and I remember that it also came from usability feedback and bugs (which were impossible to fix, lacking support of either 'auto' or 'min-content'). Without that non-zero 'flex-shrink' was unusable (especially with the original linear formula). If I understand the reverse problem correctly (do I?), pretty much every time overflow on main axis is not 'visible', you want to add "min-width:0", otherwise when random content is added it can stretch the container and totally destroy the tight layout. Right? One solution could be to fix exactly that - if 'overflow' is not 'visible', 'min-content' is not 'auto' by default. It would solve the new issue while doing the right thing for the original use case... I am not psyched about it (it's a special case for a special case...), although if you now think of a case where 'min-content:auto' gives you unwanted stretch, it will be clear where the problem is and the fix is probably to change 'overflow', not 'min-width'... Of other proposed changes, "min-width:0" and "flex-shrink:0" are both defaults that don’t work in very large share of cases and will bloat stylesheets with overrides, which will make Tab unhappy... Anyway, you do want to hear from Rossen... For me personally, special casing overflow seems worth considering. Otherwise, anything will work, as long as "auto" or an equivalent is still available. Alex
Received on Wednesday, 6 March 2013 12:18:43 UTC