Re: [csswg-drafts] [css-flexbox][css-grid] Choose a single option for resolving padding and margin percent values of grid/flex items

I was a web developer for more than five years before I encountered the (in my eyes) "weird" behavior that percentage-padding on the vertical axis resolves to the width. but I have to admit I learned it as part of the aspect ratio hack.

so for me it is both, counter intuitive and practical.

but we have a solution for things that are practical but not achievable at all or only achievable by hacks: create a spec for a feature that covers the needs.
so I'm supporting the idea of introducing new units that allow to define which axis you want to resolve against.

about the "counter intuitive" part of my analysis: yes, this part may be controversial.
but my personal experience with many of my colleagues I had to teach our explain something about CSS, especially non-webdev people, is comments like "wtf, why?" and something like this. for me this is somewhat dangerous when you think about what this makes people think about web development and web design. If I experience weird things like this early on my way of doing something on a new platform I will always be a little scared or uncertain about it. and this matches my own opinion about this specific topic.
I'd prefer to be predictable and intuitive over something like "this weird behavior has a practical use" or better in this case "there is no [obvious] practical use for the intuitive behavior".

and yes, consistency across all user agents is very important. I started web development back in the days when IE6 was still a thing. inconsistency is the worst. but right after this comes intuitiveness to merks the platform open and as easy as possible for newcomers.

but I want to raise one question, even though it speaks against my personal opinion:
wouldn't a change that removes the aspect ratio hack break [parts of] the web?

-- 
GitHub Notification of comment by Trve
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2085#issuecomment-355351899 using your GitHub account

Received on Thursday, 4 January 2018 17:54:15 UTC