Originally Posted by t3hl33td4rg0n
Given my experience developing between the major browsers, most things I've have developed worked right out of the gate with Edge, not everything, but very close. Things that didn't work quite right were usually very minor to correct. More often than not, Safari has been the troublesome browser, where it works everywhere else. Safari is the new IE.
Just a little update on this. I have recently worked on some very design heavy sites and ran into some Edge (not chromium) specific issues that I wanted to point out.
Just straight up doesn't work like it does in every other browser. To compound on that, Edge falsely says that it supports a polygon() value, when it doesn't. As a fallback, you can supply an SVG element ID containing the values, but it still doesn't clip the target element like it's supposed to.
CSS animations that are using translate, scale, and transition with some JS sprinkled in: Nope, not unless you want your web-page to look like it's having a seizure
I also ran into a weird flexbox issue that is only broken in Edge, but can't remember what it was ¯\_(ツ)_/¯.
In any case, I'm glad MS is throwing in the towel. It's a shame we can't make IE go away too