Is there a JS library/framework that lets me use this now?
Google for css grids polyfill.
Get on the CSS Grid
41–46 of 46 posts
Re: Get on the CSS Grid
#42Earlier quoted context omitted.
Yep basically.But we were alreday there with .row an .col-md-3, what's the difference between this and a table ? semantics? yeah right. By the way, tables can be made responsive too.
I can't tell if this is 100% sarcasm, 100% serious, or somewhere in-between.
> But we were already there with .row an .col-md-3, what's the difference between this and a table ?
semantics? yeah right.
I think that's a reasonable position to hold and I'd like to hear more detail of your rebuttal.
Re: Get on the CSS Grid
#43Earlier quoted context omitted.
> 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.
Conceptually, I think what they cover fits more into presentation than behavior, because its how the transition from one state to another is shown. So I don't see CSS transitions as an example of the line being drawn in the wrong place.
I'm not saying that its always clear cut or that reasonable people can't disagree on where to draw the line.
Re: Get on the CSS Grid
#44For 95% of what people want this for, CSS tables would probably work just as well ("display: table" ). The main advantage of this seems to be the "minmax" ability, and some rethinking of the api, since CSS tables are semantically based on HTML tables.
Re: Get on the CSS Grid
#45Earlier quoted context omitted.
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?
Even if my comments (those few I posted already, what shouldn't be enough of a basis for such conclusions) seem to indicate that I dislike Firefox, that is not the case. I have little against Firefox itself, so much I use it as my main browser, and the Beta as secondary. Though, I have to admit I went over with the above comment, as more than half was off-topic (and most likely the source of down voting).
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
Re: Get on the CSS Grid
#46Is this an attempt to standardize the grid layouts that everyone has to either build themselves or use a framework like bootstrap for?
This is way better.