Live data from Hacker News

Get on the CSS Grid

updates.html5rocks.com

31–40 of 46 posts

Re: Get on the CSS Grid

#31
If future browsers include default grid display systems, then [YUI's PureCSS Grid Library](0) is a modern-backwards compatability layer.

It seems even to have a "leave no browser behind" philosophy, because you can generate usable output for even IE 6 & 7.

[YUI Open Roundtable - Pure CSS with Tilo Mitra and Eric Ferraiuolo](1) is widely informative with amazing demos of each of the latest tools involved.

The docs are split across http://stage.purecss.io/grids/ and http://yuilibrary.com/yui/docs/cssgrids/ ; overall, they're sweet and concise.

0: http://purecss.io/grids/

1: https://www.youtube.com/watch?v=t4w3e-JRXy0

Re: Get on the CSS Grid

#35

Earlier quoted context omitted.

Grids are also significantly more flexible and more responsive than tables. You finally get reliable vertical centering of elements as a side-benefit. Tables got a very bad name because they were abused back when they were the only thing available for layout: "if the only tool you have is a hammer..." Yes, but sometimes data is actually tabular. Grids are good for UI layout. The web was just for documents, but not an…

> You finally get reliable vertical centering of elements as a side-benefit. Worth noting that you already get this with flexbox's align-items: center, which you can use today!

A comment on the original link stated that 'flexbox is slow', someone responded with a question; 'is the spec inherently slow or just current implementations?' but no-one elaborated.

Re: Get on the CSS Grid

#37

So we return to tables ...

We shouldn't have left tables in the first place. Design (including flexible responsive design) is ALL about grids.

Since they didn't have them in the early days, the used HTML tables, which weren't designed for that, but have lots of the needed behavior built-in.

Then came the idea to use floats, which was a horrible idea. Floats weren't designed for layout either (they were designed to, well, float simple elements, e.g let text flow around an image and such).

So designers, instead of abusing tables (which weren't meant for layout, but at least had what was needed), they started abusing floats (which weren't meant for layout AND didn't have what was needed, without ugly hacks and workarounds).

Flexbox and the Grid Layout are actual layout systems, designed for that very purpose. Finally.

Re: Get on the CSS Grid

#38

Earlier quoted context omitted.

It may seem like that, but the major difference is the layout is left to the CSS. When combined with css media queries, the grid can provide a complete restructuring of the layout completely independent of the markup which would not would have been possible with tables.

Grids are also significantly more flexible and more responsive than tables. You finally get reliable vertical centering of elements as a side-benefit. Tables got a very bad name because they were abused back when they were the only thing available for layout: "if the only tool you have is a hammer..." Yes, but sometimes data is actually tabular. Grids are good for UI layout. The web was just for documents, but not an…

>Tables got a very bad name because they were abused back when they were the only thing available for layout: "if the only tool you have is a hammer..." Yes, but sometimes data is actually tabular.

Not only that: layouts are actually tabular (grid based) themselves. That's why tables were, even if not created for layout, an untuitive fit for doing layout work.

Re: Get on the CSS Grid

#39
post #17

Great, but I feel horrible at the same time because browser just slowly reinvents everything, and is still limited to a single specific implementation. How about just make Javascript frigging fast so everyone can code their own layout system? How about standard NaCl interface for layouting? Browser needs to be an open platform, not a framework.

> How about just make Javascript frigging fast so everyone can code their own layout system? Because separating content (HTML) from layout (CSS) from behavior (JS) is a good thing, and because, particularly, being able to have content work without layout or behavior (for situations where you just need the content), and to have content and layout work without behavior (for situations where you just need static present…

I'm curious: how do you feel about css transitions? I'm being totally non-snarky here, and I fully agree in the ideals of separating the three concerns, but I sometimes wonder if the existing lines aren't drawn in slightly the wrong place.

Re: Get on the CSS Grid

#40
post #19

This proposal has been around for a while (April 2011 version: http://www.w3.org/TR/2011/WD-css3-grid-layout-20110407/ ) and if I recall correctly it has been on and off the Firefox roadmap. https://wiki.mozilla.org/Platform/Roadmap#Layout "CSS Grid Layout is coming to Firefox in 2012": http://www.2ality.com/2012/03/css-grid-layout-firefox.html So where is Firefox support for this? Was there a good reason to delay, o…

Supporting standards is pretty unimportant when you have an interface to ruin, ads to sneak in, an unasked os to support, etc... /s To be on topic, there isn't much activity in the bug topic: https://bugzilla.mozilla.org/show_bug.cgi?id=616605 . Two blockers landed in Fx30, but that is well within the statistical margins of randomness.

Wow, just scanned your comment history. You really have boner about slagging on Firefox. What is your story? Every browser has good points and bad points, but for some reason you myopically focus on the shortcomings, real or perceived, of firefox.

I understand fanboy mentality of being invested in something and over promoting it, but I don't understand where you are coming from. Care to elaborate?

Post reply on HN