W3C home > Mailing lists > Public > www-style@w3.org > February 2015

RE: [css-flexbox][css-grid] Reverting vertical % padding/margin to match block

From: Greg Whitworth <gwhit@microsoft.com>
Date: Thu, 26 Feb 2015 22:12:48 +0000
To: Tab Atkins Jr. <jackalmage@gmail.com>, www-style list <www-style@w3.org>
Message-ID: <DM2PR0301MB08798AE7693DC6BA2B511F6FA4140@DM2PR0301MB0879.namprd03.prod.outlook.com>
> So, while I understand and am totally sympathetic to the reasons we defined the behavior the way we did, I also find the counter-arguments reasonable.
> Since we're fairly intent on willfully violating the spec here, would it be okay to change the spec back to match the % behavior that Block has?
> ~TJ

Interesting, it would be helpful if you could provide an example of such bugs.

There are numerous changes in Grid and Flex that don't follow block layouts (see the changes I just emailed the list regarding abspos breaking Flipboard and Google Docs) and I would prefer not to constrain these layout modes, along with potentially newer ones due to author confusion due to older layout modes.

If Safari, Firefox, Chrome, Opera, Servo and IE implement the same thing, authors will develop sites that take dependence on this more intuitive behavior and we will have created better layout modes (and we'll hopefully see a decline in the more unintuitive box layouts with floats).

I think a good example of this is the box-sizing property where authors were used to building against content-box and had to take their margins/padding into account when producing a total width. Now, with this property numerous authors set this as the default because it is so much more intuitive and makes the most sense and this should have been the default from the beginning.

I would really like Blink to reconsider this as this is indeed our opportunity to change things for the better (as you stated). I *believe* Blink's lack of implementation is adding to the unnecessary confusion for authors due to them seeing interop differences in FF/Chrome/IE (not sure if Safari has implemented this or not).


Received on Thursday, 26 February 2015 22:13:16 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:51 UTC