3 ms·

There's plenty of cases (especially in the enterprise, where requirements can be tightly controlled) when non-Edge versions of IE can be safely dropped. I'm wor

by kozak 11y ago

There's plenty of cases (especially in the enterprise, where requirements can be tightly controlled) when non-Edge versions of IE can be safely dropped. I'm working on such a project right now, we use flexbox very extensively.

Someone1234 11y ago
That's nice for you. For public web-sites it is still non-viable. Broken versions of IE make up too large of a % of users.
- lstamour 11y ago
  Actually, if IE 10+ is the target for my site, I would totally use FlexBox. The list of workarounds is far shorter than CSS headaches used to be. Remember the terrible IE on Mac days? ;-)
SonicSoul 11y ago
interesting. are you also supporting mobile devices? any issues with iOS or Android to consider? I am considering flexbox but have to worry about supporting above. Luckily we don't have legacy IE to worry about so am hopeful. according to this [0] ie 10 and 11 are supported but with "partial support"? [0] http://caniuse.com/#feat=flexbox http://caniuse.com/#feat=flexbox
- lstamour 11y ago
  There's a list of bugs, test cases and workarounds here: https://github.com/philipwalton/flexbugs https://github.com/philipwalton/flexbugs One bug used to affect non-IE browsers but should now be fixed in all but Safari.
- kozak 11y ago
  We're developing a desktop-like single page application, so our testing on mobile is very limited. But I don't see any major issues on the few devices that we have, and caniuse.com confirms that problems are not anticipated (at least with some autoprefixing).