2 ms·

Everybody except some companies with systems locked to an older version because of legacy software they need to consume. Which also happen to be amongst your bi

Everybody except some companies with systems locked to an older version because of legacy software they need to consume. Which also happen to be amongst your big clients and despite representing 5% in your analytics, represent 20% of your potential business. Now what? Do you make your new site unusable for them? Or do you create a complex intricate fallback css which defies the purpose of using css grids?

jonnyscholes 9y ago
Then yeah CSS grid is not right for that project. But not everyone is in that camp - and some are a bit of both. We have clients like yours and then many others that don't even need IE11 based on their stats. The money saved because we can use more efficient tech like CSS grid mean more time to add features! (All our websites work in IE11 - they're just allowed to be "visually different from the approved designs" - it's a pretty good compromise for many clients!)
- jrochkind1 9y ago
  Def report back if you try doing stuff with grid that works in both IE11 and up to date browsers. I'm curious to hear how it goes from someone that did it. I've done that with flexbox, and it worked out fine for me with both IE 10 and 11, even though caniuse notes "large number of bugs" in IE11 flexbox implementation. Wasn't really a problem with my implementation. But it sounds like grid might be a different story, where IE11 implements things to an older spec with significant differences.
  - andrei_says_ 9y ago
    In a similar situation (support for ie11 and a usable site in ie10) I’ve found the susy grid system (v.2) indispensable. Incredible flexibility and precision with just a few lines of scss. I know that in a few years I’ll be writing pure css for grids, but until then it’s susy for me. I just don’t have the time or will to write multiple layers of redundant css.

2 ms·

Everybody except some companies with systems locked to an older version because of legacy software they need to consume. Which also happen to be amongst your bi

by andrei_says_ 9y ago

jonnyscholes 9y ago
Then yeah CSS grid is not right for that project. But not everyone is in that camp - and some are a bit of both. We have clients like yours and then many others that don't even need IE11 based on their stats. The money saved because we can use more efficient tech like CSS grid mean more time to add features! (All our websites work in IE11 - they're just allowed to be "visually different from the approved designs" - it's a pretty good compromise for many clients!)
- jrochkind1 9y ago
  Def report back if you try doing stuff with grid that works in both IE11 and up to date browsers. I'm curious to hear how it goes from someone that did it. I've done that with flexbox, and it worked out fine for me with both IE 10 and 11, even though caniuse notes "large number of bugs" in IE11 flexbox implementation. Wasn't really a problem with my implementation. But it sounds like grid might be a different story, where IE11 implements things to an older spec with significant differences.
  - andrei_says_ 9y ago
    In a similar situation (support for ie11 and a usable site in ie10) I’ve found the susy grid system (v.2) indispensable. Incredible flexibility and precision with just a few lines of scss. I know that in a few years I’ll be writing pure css for grids, but until then it’s susy for me. I just don’t have the time or will to write multiple layers of redundant css.