Microsoft Edge - EdgeHTML interoperability

This article is part of a series of posts detailing specific compatibility tollgates for a modern web, and how you can take action to make sure your site works as intended in the world of modern web browsers:

EdgeHTML interoperability

Previously we stood on the barricades proclaiming “adhere to standards!”

That’s still true. Sort of.

Reality though is more “adhere to interoperability”.

The days of quirks mode, compatibility issues or rendering issues should be long gone.
The only thing now standing in the way between a good, universal web and your customers is your own code.

You shouldn’t have to worry about sending your markup in different forms to different browsers – the web should just work and you should only have to send your awesome markup one way.

Why is it important?

Your users will get their best experience in their preferred browser. You can spend less time maintaining separate code bases for various modern browsers including Microsoft Edge.

What will we look for?

We check if the webpage may include HTML markup that treats Microsoft Edge differently from other modern browsers.

How can you fix it?

We recommend your site to send your markup to all modern browsers and then include Microsoft Edge in your test matrix. This will also help you progress towards maintaining one code base in the future.

Where can you learn more?