4 ms·
You don't have to make pages that look identical in every browser. Make something that works for everyone and then use newer browser features to make it as good
by onion2k 9y ago
You don't have to make pages that look identical in every browser. Make something that works for everyone and then use newer browser features to make it as good an experience as possible depending what features are available. CSS even has the "@supports" feature for doing it - https://developer.mozilla.org/en-US/docs/Web/CSS/%40supports https://developer.mozilla.org/en-US/docs/Web/CSS/%40supports
- cvsh 9y agoThe problem is that grid is best used for overall page layout... which is part of your CSS least amenable to progressive enhancement.
- c-smile 9y agoIf to speak about layout methods @supports will not help you but will force you to do the job twice. If you can do your layout without flex boxes why do you need to create second version with them at all?
- steinso 9y agoDepends how you do the job, if you initially design for mobile you can use the mobile layout for everyone that does not support grids, and add grids for the traditional desktop layout. Since grid layouts are created as a list of elements, this workflow is actually pretty efficient.
- onion2k 9y agowill force you to do the job twice That's one way of looking at it. I prefer to see it as writing features that only certain users will benefit from. In the case of layout, I tend to give users with older browsers a much more basic, linear flow (just making the semantic HTML work really), and then add in more complex layout using what tech is available. That's not really doing the same work twice in my opinion.