41–50 of 90 posts
Is there a good pollyfill for older browsers?
The speaker suggests serving up mobile layout for older browsers and this is the pattern we are following at my company.
yes grid is awesome but how to deal with polyfill is the question
Earlier quoted context omitted.
The speaker suggests serving up mobile layout for older browsers and this is the pattern we are following at my company.
what does 'serving up mobile layout' exactly mean? Thanks. yes grid is awesome but how to deal with polyfill is the question
Earlier quoted context omitted.
I disagree. It is possible to generate a wide variety of layouts using this and other purely declarative approaches. If producing a layout requires the use of "Turing-complete" semantics, then JavaScript is available for the purpose. I would argue if your layout becomes that complex you might consider simplifying. There is a long-standing trend of adding scripting into declarative environments to allow greater capabi…
I'd agree with you if web pages were "static documents", but they aren't and never were. They've always had to adjust to different screen sizes, and quickly became interactive applications, and now have to adjust to radically different pixel densities.
When I see devs saying "Just do it all in Javascript" I have to assume they aren't actually that familiar with CSS. First off Javascript simply manipulates CSS properties anyway when it comes to styling, and writing a system that completely ignores CSS and renders its own way is far more complex without any clear benefit.
Any idea why the grid is 1-indexed instead of 0-indexed?
Tables. They're back!
Tables. They're back!
Wrong. Tables impart meaning to user agents (browsers, screen readers, google bots, etc) and as a side effect they have a default visual style that is useful for some layouts in some limited situations (but without any kind of fine-grained detail that most modern designs call for -- ESPECIALLY when making responsive designs that work across different screen widths). CSS Grid, on the other hand, is a tool specifically…
Now if it was a full constraint system, that would be more impressive.
If you need to support IE 10, 11, or Edge then Grid is broken. Microsoft's browsers follow an older spec than Chrome/Safari/Firefox. Microsoft are going to fix Grid in Edge 17, but no release date yet. Unfortunately this is my life right now. When Chrome and Firefox dropped support for NPAPI a lot of enterprise customers intentionally moved their users back to IE 11. The loss of NPAPI has ironically increased IE 11's…
I've used grid with IE11. You need to add some extra prefixing noise to your css. The way you identify grid elements is different and it sucks to duplicate the layout information. But it most definitely works.
Which means, if you need to support IE10, you need a whole parallel set of styles. There's no graceful degradation when it comes to overall site layout, unless you're willing to serve the single-column mobile version to older browsers.
Earlier quoted context omitted.
I'd agree with you if web pages were "static documents", but they aren't and never were. They've always had to adjust to different screen sizes, and quickly became interactive applications, and now have to adjust to radically different pixel densities.
And all of that works just fine with CSS. CSS has problems, but more to do with scoping or lack of a grid-based layout system (until now). When I see devs saying "Just do it all in Javascript" I have to assume they aren't actually that familiar with CSS. First off Javascript simply manipulates CSS properties anyway when it comes to styling, and writing a system that completely ignores CSS and renders its own way is f…
There’s a reason all the “powerful CSS layouts” are all poor re-iterations of printed pages. Once you want actual layout, you end up carefully positioning everything with Javascript.
And by actual layout I mean things like Sencha (easily half of which still cannot be implemented in CSS without)