[deleted]
CSS Grid – Table layout is back. Be there and be square
11–20 of 280 posts
Re: CSS Grid – Table layout is back. Be there and be square
#12I'm really excited for this. I've been using pure flexbox layouts for a while now, but it still has one major problem, in that your HTML structure still contains layout and positioning information.
Everything is either a column or a row, so in the example layout in the link, you'd need two container divs. Whereas the grid example can be done without any.
Re: CSS Grid – Table layout is back. Be there and be square
#13Why is this problem so hard when CSS does so much for node positioning? Why not create a simpler standard once and for all?
We had a simpler standard in 1995. It was called tables and it did this exceptionally well and more importantly was easy enough for even amateurs to understand. And then armchair demagogues decided that markup should no longer be used for markup, setting web layout back decades and creating the field of web designers whose major accomplishment was understanding stupid div hacks.
It's pretty amazing, isn't it, the type of infinitely useless brain loops we can get stuck in. Especially when we fail to take a step back and ask the question "Is this really the right way?".
Re: CSS Grid – Table layout is back. Be there and be square
#14Re: CSS Grid – Table layout is back. Be there and be square
#15Why is this problem so hard when CSS does so much for node positioning? Why not create a simpler standard once and for all?
We had a simpler standard in 1995. It was called tables and it did this exceptionally well and more importantly was easy enough for even amateurs to understand. And then armchair demagogues decided that markup should no longer be used for markup, setting web layout back decades and creating the field of web designers whose major accomplishment was understanding stupid div hacks.
It did it exceptionally poorly, and out-of-order source that was damn near impossible to modify was the norm.
Re: CSS Grid – Table layout is back. Be there and be square
#16The biggest game-changer to me seems to be the last example, with `grid-template-areas`. I could probably explain this in a matter of minutes (as opposed to flexbox).
Re: CSS Grid – Table layout is back. Be there and be square
#17> Short of taking care of sizing the elements yourself, sadly, you can't have both a vertical and horizontal rhythm by just using flexbox alone. Accompanied by https://developers.google.com/web/updates/images/2017/01/css... I'm pretty familiar with Flex but I simply don't understand and the diagram doesn't help. What does 'rhythm' mean in terms of layout? Taking a guess (which I shouldn't be), I can make https://deve…
OP is likely referring to vertical rhythm in typography:
Re: CSS Grid – Table layout is back. Be there and be square
#18Just to point out this page doesn't scale properly on iOS when you pinch to zoom. CSS TFW.
Re: CSS Grid – Table layout is back. Be there and be square
#19If we all had something like Display Postscript, this layout thingamajig would be delegated to libraries, and we wouldn't have to ask the browser deities to bestow new gifts upon us. Good adaptive layout would be closer to a new version of jquery and less Windows XP Service Pack 51.0.2b.
(We also would have more sites that looked liked late 90s Flash, but then again, we're moving that direction anyway, just with more effort and convoluted design)
Re: CSS Grid – Table layout is back. Be there and be square
#20Earlier quoted context omitted.
We had a simpler standard in 1995. It was called tables and it did this exceptionally well and more importantly was easy enough for even amateurs to understand. And then armchair demagogues decided that markup should no longer be used for markup, setting web layout back decades and creating the field of web designers whose major accomplishment was understanding stupid div hacks.
It's pretty amazing, isn't it, the type of infinitely useless brain loops we can get stuck in. Especially when we fail to take a step back and ask the question "Is this really the right way?".
In 1995 I was creating a layout engine for a UI manager (personal project). It was simpler to use and I had better primitives. Had I known then that in 2017 we will still discuss about layouts, I would have face palmed so hard.
In my opinion CSS's worst sin is that it does not include basic experience from other programming languages: variables and name scoping. It's a minefield of namespace collisions and superfluous repetitions.