[AWebOfBrown]

Is it still the case that one realistically needs to write their layout in flexbox as a fallback? Last I checked grid support was about 87% globally. I learned grid at one point but then just ignored it on the basis that if I had to write everything in flexbox already, why do both? Would love to know if this is a false assumption.

[modernerd]

Use a simple mobile-first layout, then add "@supports (display: grid)" to enhance the layout for browsers that support grid.

Mobile OS browsers and IE 10 will get a usable experience that way without having to write flexbox fallbacks.

“Internet Explorer + CSS Grid????”

https://www.youtube.com/watch?v=7msERxu7ivg

MDN: Using feature queries

https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Grid_La...

[merb]

> “Internet Explorer + CSS Grid????”

well the original css grid spec actually did came from microsoft (https://www.w3.org/TR/2011/WD-css3-grid-layout-20110407/)

That's why it's only partial supported, they never updated it to the current version.

[deckard1]

I think the point is, you have to write the fallback anyway. There really is no "enhanced", as they are two different ways to reach the same solution. The user won't notice a difference, and no sane person wants to do the same thing twice just because one method is slightly cleaner.

This is why CSS grids have been a nonstarter for most of us.

[modernerd]

It depends if your use case accepts that a site can look different in older browsers. You don't have to write a fallback if people are okay with that.

If your project's stakeholders are prepared to accept that IE 10/11 users won't see the same as Chrome users (I use, “in the same way that those on mobile won't see the same as those on desktop, older browsers such as IE 10 will also see a simpler layout”), then progressively enhancing a mobile layout with CSS Grid is a fine approach.

I accept that this can't always be the case, though. But I don't consider CSS Grid a non-starter for most sites. Browser support is now good enough that I look to use it wherever possible, and try to educate people still stuck in pixel-perfect across all devices -land.

[andrei_says_]

Isn’t ie11 incompatible with the official grid spec?

[modernerd]

Yes — I should have written IE10/11. Neither supports @supports, though, so that's still a good way to progressively enhance for grid.

[andrei_says_]

Unfortunately we’ll need to build our new site to look nice for IE11, too, as the stakeholders are locked on windows7.

[modernerd]

That's unfortunate and likely will require a flexbox/float-based fallback.

[andrei_says_]

Suzy Grids 2 is float based, a pleasure to work with and covers the old browsers. I'd love to switch to CSS grids but will have to wait another 5 years it seems.

[Bogdanp]

Depending on your use case, you might get away with building your layout for mobile and then grid-ifying it for larger devices. That way those browsers that don't support grid will get the mobile version.

[sametmax]

Really nice idea. Never though about this one. And since mobile browser are usually the ones with old engines, it make sense twice.

[tripzilch]

Eleven years ago I was freelance/part-time web developer, specialised in frontend work. If somebody from the future had shown me this comment (quoted below), even though I'd have no idea what "flexbox" or "grid" means, I'd understand, smile and say plus ça change, plus c'est la même chose ...

> Is it still the case that one realistically needs to write their layout in flexbox as a fallback? Last I checked grid support was about 87% globally. I learned grid at one point but then just ignored it on the basis that if I had to write everything in flexbox already, why do both? Would love to know if this is a false assumption.

[sbouafif]

It was still true 2 months ago. I did the same as you and stop using it.

Here's a list of existing bugs that prevent me using it in production https://github.com/rachelandrew/gridbugs

[sureaboutthis]

flexbox was not created for, and should not be used for, page layout. It's to be used for for a series of elements that flow in one direction only and designed for sections of a page, not a whole page.