Experimental support ala prefixes is still happening, they just stick it behind prefs now, so devs can turn them on to experiment with, but they can't be used in production sites. This was done in response to webkit becoming the new IE6, especially in mobile land, where countless (shitty) devs were using prefixed properties as essential parts of their stylesheets, thus breaking sites for other perfectly good browsers like Firefox and Opera.
Also grid isn't really a case of IE being forward thinking, Microsoft just happened to create the grid spec, so it's more a case of pushing their own solution, rather than being fast on implementing a new tech.
Re:Mozilla in 2013
by robin_reala on Monday December 16, 2013 @03:27PM
(#6917581)
I believe MS came up with the grid spec, or at least the original draft editors were three MS employees and glazou: http://www.w3.org/TR/2011/WD-css3-grid-layout-20110407/ . This was published five days before the first platform preview of IE10.
It does seem like a neat spec though, I’d welcome inclusion as another tool in the box.
We (Bloomberg) hired Igalia to help put some resources on implementing CSS Grid. The original MS authors didn't like the initial spec so they've been working on an improved spec w/ others (Google, Igalia) and Igalia is landing code for it in both WebKit and Blink. So it is definitely moving forward..
> Mozilla has a new 'avoid vendor prefixes' thing
FWIW, Google Blink also takes this position: http://www.chromium.org/blink#vendor-prefixes
> stable spec
I'd really like to see more vendor prefixes for support. I mean, basic flexbox support was rolled out quickly, and the spec changed like three times. Mozilla has a new 'avoid vendor prefixes' thing, which I think is the wrong approach. I'd rather just use a tool like autoprefixer to generate all of the browser-incompatible CSS until we can all agree.
I can't believe I am praising IE for being forward thinking! (they have full CSS grid support, per the draft)