4 ms·
I still have to support IE11 and the fact that it doesn't support modern API its one of the reasons I hate it with passion. Something like not supporting css va
by alserio 5y ago
I still have to support IE11 and the fact that it doesn't support modern API its one of the reasons I hate it with passion. Something like not supporting css variables is seriously limiting. As second place I'll put the unusable dev tools. Spec compliance is more of a problem for css than js. I concede that with previous IE iteration the problem was much more worse.
- G3rn0ti 5y agoAt least it has dev tools. IE6 didn’t. So every time JS failed I had to alert myself into the heart of the problem…
- alserio 5y agoI'm grateful to the previous generation of web dev, and their suffering to avoid us younger generations their pain.
- deergomoo 5y agoI agree, but I will say that if your site doesn't rely on newer CSS features, IE11 is still surprisingly easy to deal with. A whole lot of cutting-edge JavaScript can be polyfilled/transformed to work on IE11 (automatically in most cases, with something like Babel), and the module/nomodule pattern can stop that polluting your bundles for modern browsers. It also has decent flexbox support (just a few oddities easily worked around IIRC), although its grid implementation is incomplete and uses an older version of the spec that in most cases just isn't worth the effort.