We treat Chrome/Safari/Edge/FF all as 1st class browsers and haven't had many problems (aside from Safari lacking U2F and exotic CSS props like motion-path).

mix-blend-mode is another thing that EdgeHTML doesn’t support that I was using for a bit, but I stopped using it because I kept finding critical bugs with it in Chromium, most notably https://bugs.chromium.org/p/chromium/issues/detail?id=992398 which was impossible to work around, simply stopping rendering the page after 8192px!

1. The :focus-within CSS pseudo-class doesn't work

2. object-fit only works on images

3. These SVG loaders don't work: https://samherbert.net/svg-loaders/

I'll be glad if/when Edge (blink) is deployed with a windows update.. the sooner the better, as far as I'm concerned.

We've been using TypeScript for all scripts longer than ~20 lines for years - so we got async functions for free (it compiles async/await TypeScript functions to IE11-compatible ES5 just fine).

Not to mention all the issues you'll have if you try to use CSS Flex or Grid.

Support IE11 only if you absolutely must, is my advice, and do that with differential serving: https://philipwalton.com/articles/deploying-es2015-code-in-p...

https://calendar.perfplanet.com/2018/doing-differential-serv...

I'd rather not support a dead browser, that's been dead for years now, that has clear replacements and alternatives. Not to mention security concerns above and beyond development pain..

    [1] https://caniuse.com/#feat=async-functions
    [2] https://caniuse.com/#feat=fetch

The beauty of the approach is that the big pollyfill payloads are only borne by the users who choose (or likely are forced by employers) to use those browser versions.

IE11 is another story, though.

It's a pet peeve of mine that apps don't support Edge/Trident, Vivaldi, etc. It's easier to write cross-browser code than ever, but it seems like we're in the process of reverting back to the bad old days when IE6 was the only browser people supported, but it's Chrome now instead of IE.

People are literally doing User Agent Sniffing again, and even though these browsers carefully craft their UA string to pass naive checks, the sniffers are hacking around that and urging me to "Download Chrome" to use a website.

Notable Offenders: Google Hangouts, and banks. Not impressed, Google.

I lived through the IE6 years, so I was never thrilled with any version of IE I had to support, but Edge was actually a good browser. Strange UI, solid engine.

...and that's one of the reasons everyone hates Edge. I'm a long-time IE user and that stupid dumbed-down UI is absolutely repulsive. If they'd just put the Chromium engine in the normal IE UI I bet they'd get far more users naturally using it.

I would be surprised if they still want to be a customer.

I just can't get behind this lazy "small team" excuse; it's really unnecessary hubris.

I worked on a "small team" of 1 (just myself - I was the only dev) for several years on an enterprise webapp. The kind that does complicated stuff - not a simple CRUD app. [Sidenote: I would have killed for a team of three!!] Yet I supported Edge since the day it came out and never dropped support of IE. In fact, I even supported old versions of IE (7 and up) until the day Microsoft EOLed older version of IE (that was January 12th, 2016, FWIW). It honestly isn't very hard these days. Annoying sometimes, yes, but not difficult.

I suspect the agility of any team is heavily influenced by not just numbers, but tech debt, and other choices.

All future work we do is compatible with Edge, it's not like NOTHING works with Edge, but to say "We support Edge"... customers expect that to mean everything.

Fortunately I don't think we'll have to have that conversation anymore.

Still not an excuse to alienate your customers who want to use a browser that comes with their OS. Enterprise customers never want to go through the hassle of installing external software company wide just to use your services.

Lots of customers still on Windows 7... that's bad, but we can't change that.

Why though?