kylealden

Have you used a Surface recently? The touchpads have been great for a long time, and the newer ones have advanced haptics that Macs don't have yet.

Worth noting that this feature is limited to installed PWAs, so you'd either have to convince the user to install a PWA via the URL bar affordance (which already requires real HTTPS and respects the LOD), or to manually install a site-as-app through the browser's (relatively buried) UI, at which point you get the same site you're already on, but with a new titlebar. That seems like a pretty unrealistic vector and is much less complex then just getting users to install an .exe.

That said, even with the Window Controls Overlay, the minimal browser controls (close/restore/minimize) are mandatory, as is the browser-owned "..." menu which includes basic trust information for the site as well as app controls (uninstall, permissions, etc.).

This was fixed more than a year ago, FWIW.

I'm not sure where you get the idea that GDPR doesn't apply to operating systems.

You can control every facet of your diagnostics in Windows settings, see every bit of data collected about you (both locally and on the cloud), and delete it all.

"teh" is a basic spelling error, but I bet you've let it slip through somewhere before

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.

Per the blog post, we're not localized broadly in the preview, but will be adding more locales/languages as we head towards a stable release. Hope you'll try it again!

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)