To second what Navarr said, I don't really see IE issues these days unless it's on a site that needs to support versions prior to IE9. As often as not, issues in modern IE are due to developers writing code that targets only a single vendor-prefixed version of an API instead of supporting standards, which makes IE look deficient (instead of that sloppy developer) even when it has good support for the APIs that a site uses.

To name just one thing that IE still doesn't support: setting the download attribute on a link. Neither does Safari.

This makes it very clumsy/impossible to write real web apps that need to save to the local file system. The scenario is generating a document client-side using JavaScript. Now you want to let the user save it. In Firefox, Chrome, Opera, and no doubt others, this isn't a problem. Just set the download attribute on the link to the file name you want to use.

You can use this API onclick to do the same thing: https://msdn.microsoft.com/en-us/library/ie/hh673542%28v=vs....

Now, let's talk about Chrome's pointer events support...

I'm glad I looked up rule 34 real quick; I don't expect there's porn of this.

What's actually involved here is http://en.wikipedia.org/wiki/Poe%27s_law

These days most of my bugs are Firefox acting differently than I expect it to (though perhaps compliant to standards).

I haven't really had to say "IE Issue" unless I was dealing with 8 and lower.

web audio api :/