Get on the CSS Grid
updates.html5rocks.com
updates.html5rocks.com
"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, or was it just other priorities? Did flexbox take much longer than expected?
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.
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?
What I do not like is some of the decisions Mozilla leaders made lately. For example, I am clearly against the Directory Tiles or Australis in it's current form, but I support the rapid release cycle, as it clearly threw back Fx into the race and is now one of the top two browsers.
what was also hasty without the 'addons are compatible by default' and Mozilla Maintenance Service
http://blogs.igalia.com/mrego/2014/03/13/welcome-css-grid-la...
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.
I always liked the flexibility of using that layout manager (although I always managed it via visual editors) so if this does reach mainstream compatibility it could be good!
As comments on the article point out, it seems to overlap with FlexBox quite a bit though.
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 any more. So now we need good ways to lay out UIs.
Worth noting that you already get this with flexbox's align-items: center, which you can use today!
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.
semantics? yeah right.
By the way, tables can be made responsive too.
I think that's a reasonable position to hold and I'd like to hear more detail of your rebuttal.
http://demos.jquerymobile.com/1.3.0-beta.1/docs/content/cont...
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.
If layout were in JS (or PNaCl), we wouldn't be able to run it off the main thread, or parallelize it in Servo, or experiment with running it on the GPU. We would also lose the ability to do text reformatting on mobile, accessibility would be harder, etc.
To elaborate in regards to running CSS off the main thread: We got very lucky that IE's extensions to allow JavaScript in the middle of CSS evaluation (and also possibly XBL) never caught on, and so CSS can be done more or less entirely independent of the main JS event loop (unless the styling is performed in response to a direct JS query, e.g. getComputedStyle). If layout were performed by JS, there would be no hope: layout could perform arbitrary JS manipulations and we would be no choice other than to stall the main event loop while styling is happening (as current browsers do). But because CSS is largely separated from JS, we can just run it off the main thread and allow JavaScript to run uninterrupted by layout.
Yep. Not sure why they didn't just copy WPF or even Android's way years ago.
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 presentation) are important.
I'm not saying that its always clear cut or that reasonable people can't disagree on where to draw the line.
What's changed in this version?