- From: Lorin Halpert via GitHub <sysbot+gh@w3.org>
- Date: Thu, 01 Apr 2021 06:30:27 +0000
- To: public-css-archive@w3.org
Thanks for the blazingly fast reply Rachel, seems my triage ping was unnecessary! The solution you linked seems like a fantastic cure-all for all margin related woes that I look forward to in the far future once it's both implemented and passes the ~95% 'CanIUse' threshold that most of the projects I'm involved in utilize. I'm aware of the general convention of letting 'old dogs lie' and that changing the way an existing implementation handles things outside the scope of security/privacy/depreciation is considered 'a bad thing'. However IMHO, even though it may break a few pixel-perfect layouts that rely on this exact behaviour - it is a trivial enough case, esp. since it only influences the positioning of the first child, to warrant a revision for 'the greater good' due to its non-intuitiveness. The amount of time saved in aggregate for developers and designers that experience the behaviour and try to remedy it without a 'hack' is enough of a justification for me. Browser DevTools simply don't provide insight into whether an element is experiencing margin collapse at the moment (as seen in demo) - and even then a developer would have to know what to look for. -- GitHub Notification of comment by alystair Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6170#issuecomment-811678583 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 1 April 2021 06:30:28 UTC