61–70 of 90 posts
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…
Earlier quoted context omitted.
It doesn't with IE10 though. And there's no way to fall back to flex or another column system. 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.
what's wrong with giving older browsers a different experience?
Earlier quoted context omitted.
I love not having to care about whether websites I make work on broken or incapable browsers! :-)
So you like being lazy ... a technical challenge comes your way and you hope others fix it for you. This is the hipster frontend engineer attitude. Not to be mistakened for real frontend engineers who create robust sites for paying customers. Enjoy your world and ill enjoy the enterprise dollars. I like coding. I dont complain about the challenge.
For all you know, they build websites or applications that don't have any need to run on older browsers, or at the very least, there are diminishing returns.
There's always an opportunity cost. While you're building support for older browsers, they could be adding valuable functionality to their software.
Which is more valuable depends on the situation.
Earlier quoted context omitted.
It doesn't with IE10 though. And there's no way to fall back to flex or another column system. 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.
what's wrong with giving older browsers a different experience?
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…
Reminds me of GridBagLayout in Java Swing. Can anyone here who has experience with both confirm this?
Tables. They're back!
Also kudos to the speaker, Morten Rand-Hendriksen, that was a very enjoyable presentation!
I giggle a little bit inside when web designers say "We shouldn't use meaningless tags that exist only for layout. We should use semantic ones, like and !". Except that, uh, "header" and "footer" themselves are layout terms. They're just a metaphor for a document as a body (" ") with the head at the top and the feet at the bottom. It's not like the contents of a tag have anything to do with feet. We call it "semantic…
Do they care more about its structural position? Then name it by structural position. Do your teammates care more about a component's logical relation? Then name it by its logical relation. Do they care more about the actual content? Then name it the EULA component.
But one way or another, based on the modern way of web dev where an interface is divided into components, any team inheriting a project will need to understand Y components explaining X pages no matter what. Naming is helpful, but the distance from good naming to great naming won't be a big force multiplier.
Jen Simmons and Rachel Andrew have done really great work on making CSS Grid sensible to comprehend. I cannot recommend their resources enough. - http://labs.jensimmons.com/ - https://gridbyexample.com/