I think IE 10 and 11 have partial CSS Grid support, so not all features will work. Here's an article about working with grid and those older browsers: medium.com/@elad/supporting-css-gr...
It's immensly important to know that in IE10 auto-placement isn't supported in grid, meaning you'd have to manually place every item.
To me, it's safer to build grid for the browsers that include full support and then include reasonable fallbacks for browsers that only partially support or don't support grid.
Even better to build the "fallback" first, then enhance with grid if @supports passes!
Well IE 10 to Edge use a different implementation of Grid, so this makes it pretty tricky. For example alignment and gutters don't even exist in those browsers. Additionally and more importantly Grid is only commercially useful under the right conditions.
Some maybe's could be:
Your website only attracts visitors that are likely to use very modern browsers. HackerNews? Dev.to? At 88%ish it's really playing with fire tbh.
I've recently read Webpack could allow a developer to create targeted CSS bundles for different browser types, thereby allowing you to the those not in 80s with Grid and those still watching Back to the Future with Tables and such.
Those are basically my two many thoughts on Grid compatibility. I'm no expert, but it's where I've settled for now.
Lastly a point I think about personally is that most sites are developed pre-Grid and so I still need to be developing those skills that I need day in and day out regardless of Grid's penetration due to the simple fact that even if I write a new site in 2 years using Grid I'm likely still needing to apply Grid against some legacy components and so even then my knowledge of those 'historical' specifications is still likely mote necessary thab Grid.
Ps. I'm learning Grid, but I just am in no rush to get to the finish line with it.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
ok, but what about IE 10 or 11?
I think IE 10 and 11 have partial CSS Grid support, so not all features will work. Here's an article about working with grid and those older browsers: medium.com/@elad/supporting-css-gr...
It's immensly important to know that in IE10 auto-placement isn't supported in grid, meaning you'd have to manually place every item.
To me, it's safer to build grid for the browsers that include full support and then include reasonable fallbacks for browsers that only partially support or don't support grid.
Even better to build the "fallback" first, then enhance with grid if @supports passes!
Well IE 10 to Edge use a different implementation of Grid, so this makes it pretty tricky. For example alignment and gutters don't even exist in those browsers. Additionally and more importantly Grid is only commercially useful under the right conditions.
Some maybe's could be:
Your website only attracts visitors that are likely to use very modern browsers. HackerNews? Dev.to? At 88%ish it's really playing with fire tbh.
I've recently read Webpack could allow a developer to create targeted CSS bundles for different browser types, thereby allowing you to the those not in 80s with Grid and those still watching Back to the Future with Tables and such.
Those are basically my two many thoughts on Grid compatibility. I'm no expert, but it's where I've settled for now.
Lastly a point I think about personally is that most sites are developed pre-Grid and so I still need to be developing those skills that I need day in and day out regardless of Grid's penetration due to the simple fact that even if I write a new site in 2 years using Grid I'm likely still needing to apply Grid against some legacy components and so even then my knowledge of those 'historical' specifications is still likely mote necessary thab Grid.
Ps. I'm learning Grid, but I just am in no rush to get to the finish line with it.