I don't mean to be so disparaging, but Microsoft really should just take IE out back and shoot it.
Sure it has overstayed its welcome. But I hate the revisionist attitude of some, who were still in school when all this went down.
Edit: see details in post below.
The people over at Microsoft are not idiots - even though Microsoft is no longer the new hotness, they still pay developers well, and have some pretty tight engineering going on. So when you say "The Event constructor is broken out of the box", my first instinct is to assume that the Microsoft engineers have implemented the constructor in their way for reasons that you're not smart enough to have grasped.
But, as I said, I know that you aren't a young inexperienced programmer, so you probably have some good reasons to make the claim, which leads me to the point of this rambling post - why is the Event constructor broken in IE? I'm curious to know what specific problems you have with it.
IE11 has no CustomEvent constructor. You have to polyfill it with https://developer.mozilla.org/en/docs/Web/API/CustomEvent. Microsoft's official Twitter account @iedevchat has pointed people to the same one: note the article article says for IE10, but the issue and fix is required for IE11.
It's a simple fix, but CustomEvent is ancient, and it's surprising what didn't make it into IE11.
They promised that they have changed in regards to that, but those are just words in the wind, time will tell on that. Also, they were lagging behind HTML5 standards for a long time, then they sort of caught up, now they are lagging behind on ECMAScript 6 features.
Every time I check, it is Microsoft's fault that I still can't use an otherwise widely implemented feature.
Quality implementation and standards adoption is the name of the game in the browser market. After 10+ years in that market, my opinion is that they have neither. The only reason they are still playing is end-user and corporate inertia.
That's no longer the case.
> They promised that they have changed in regards to that, but those are just words in the wind, time will tell on that.
No, they aren't just words. For example, in the ES6 committee everything I've heard is that Microsoft has been doing fantastic work, right now.
> Quality implementation and standards adoption is the name of the game in the browser market. After 10+ years in that market, my opinion is that they have neither.
I don't think that's fair either. The implementation of canvas in IE9, for example, is a very high quality Direct2D-based GPU implementation. (D2D is still arguably the best widely-used GPU vector graphics implementation around.)