5 ms·
Why not both? Global flexbox support is >96% and in the US it's >97%. Unless you're aiming for a 1:1 pixel-perfect experience in crappy old versions of IE, it'
by freshyill 10y ago
Why not both? Global flexbox support is >96% and in the US it's >97%.
Unless you're aiming for a 1:1 pixel-perfect experience in crappy old versions of IE, it's negligibly simple to detect IE (or lack of flexbox support), and just use something else. You can usually get pretty close to a lot of flexbox layouts with display: table and related properties, and also falling back to floats for others.
In a worst case scenario, you can provide old IE with a more mobile-like experience and just let things stack up.
- deleted 10y ago[deleted]
- spdustin 10y agoEnterprise in the US. IE9 still rules, in many cases. I actually work all over this space, do not tell me otherwise. And now I have to maintain two codebases?
- vinceguidry 10y agoYour problem is actually simpler than if you had to maintain modern consumer-facing web apps, which have to deal with users across three broadly-defined screen sizes and a variety of mobile APIS. If you're serving the enterprise, then you can make assumptions about your audience that greatly simplify development.
- spdustin 10y agoThose assumptions are nowhere near as simple as you think when you are in a space that supports a large majority of all enterprise. You would shudder to see what real-world browser support is like when you write software to be used in that space.
- intrasight 10y agoMy experience is that that ceased to be the case about a year ago. Now everyone also has Chrome.
- spdustin 10y agoYour experience isn't in healthcare, finance, military, manufacturing or oil and gas (to pop a few verticals off the top of my stack), it would seem. Literally 80% of my (adult, American-enterprise-employed) students in 2015-2016 so far have IE9 as their desktop standard, and have to beg for a special exemption to be allowed to install Chrome or Firefox.
- moron4hire 10y agoI've done those verticals, too. We always had Firefox. I don't know what it's like now. That was 10 years ago. (AKA sit down and shut up with your bullshit "sit down and shut up"s)
- spdustin 10y agoI literally deal with students in every class, a not-small percentage of students, that are disallowed by domain policy from installing another browser.
- Roboprog 10y agoI know :-( Give it a year. Without MS support, they will be forced to give up these older versions. Of course by then, IE 11 will seem quite "vintage", but that's life.
- moron4hire 10y agoI literally think you're an asshole for thinking you know everything about how enterprise works. IT can be brow beat just as hard as developers. They will change whatever domain policies you make them change. Quit being a pushover.
- intrasight 10y agoBesides military (haven't done that in 10+ years), I'm in all those other verticals and more. All desktops now have IE11 (because MSFT pretty much says "you must") and Chrome.
- Roboprog 10y agoBeen there, done that. But you might mention to bosses/clients that MS no longer supports/patches anything older than IE-11 on desktop versions of Windows. They are most likely using an un-patch-able version of Explorer. Virii, Trojans and Hacks, oh my! https://www.microsoft.com/en-us/WindowsForBusiness/End-of-IE-support https://www.microsoft.com/en-us/WindowsForBusiness/End-of-IE...
- spdustin 10y agoExcellent advice that I give my students, and readers here will be well-served in following it. I don't even want to admit how many managers come back to them with "we mitigate that risk with user education, we have too many legacy (blah blah blah)." There's always some excuse, isn't there? Usually within departments, but once executive-level hears this sort of thing, they tend to at least investigate what the real risks are. So I'm adding on to your advice to other readers to suggest they "go higher" with their security warning. Man, I wish we lived in a world where management understood that people are shockingly good at finding ways of not doing what they're told!
- bigger_cheese 10y agoMy work "upgraded" to IE 11 late last year. The problem is so much of our internal infrastructure was built to target IE 8 (or earlier) that when our information services guys deployed IE 11 they forced it to run in compatibility mode. Now you have to go through this endless dance of Enable/Disable compatibility mode depending on what site you are trying to visit. We have a lot of non technical users so as soon as you ask them to delve into menu options to use some added functionality on a site you lose them. Even technical users hate this so most people sideload chrome. However a large number of workstation are locked down and those people have no option but to continue with IE.
- extrapickles 10y agoWe use nw.js (customizable webkit browser) to provide an "application" for those customers that only have IE9 so we don't have to support IE9 in the web application. Sales pages still need to support IE9 though as they use IE9 to find the product.
- netghost 10y agoAt the point when you write fallbacks for IE, you might as well just use an approach that works for all your supported browsers, otherwise you've got twice as much to verify and maintain. Check this out for an alternative to flexbox if you can't ignore that last n% of your users: https://kyusuf.com/post/almost-complete-guide-to-flexbox-without-flexbox https://kyusuf.com/post/almost-complete-guide-to-flexbox-wit...
- freshyill 10y agoWith flexbox and a fallback, you're future-proofing. If you go with floats or something worse, you're working around yesterday's constraints.