[kylealden]

The version of Edge you're linking to on HTML5Test there is two years and four major versions out of date. Edge 16 is more than 100 points higher on HTML5Test.

More generally, there's a lot more to making the web great than a blind sprint to adopt every API. Just because it isn't shipping doesn't mean Microsoft isn't a (very) active participant in the standards conversations, testing behind flags, etc. That is a huge part of moving the web forward.

Take Grid as an example - we were the last browser to ship the updated spec, so you could say we "held it back." But we also originated the first version of the spec and worked closely with the community, standards bodies, and other browser vendors on making sure what ultimately shipped cross-browser this year was great, useful, and interoperable. Is that holding the web back?

(Disclaimer: Edge employee)

[mixedbit]

To add another example, WebVR API cleanup was inspired by Microsoft that joined the group working on this API. Edge isn't yet shipping WebVR, but they are helping with the work.

[kylealden]

Good example! Though, for the record, WebVR 1.1 is shipping in EdgeHTML 15. Fair to call it a preview, since consumer headsets won't be available until later this month with the Fall Creators Update, at which point end-to-end support will work out of the box.