Why does http-equiv="X-UA-Compatible" content="IE=edge,chrome=1" is not validated in W3C Validator?

18,790

According to this discussion in the W3C, using the chrome=1 part is not allowed.

You can pass the validation by using just like this:

<meta http-equiv="X-UA-Compatible" content="IE=edge" />
Share:
18,790

Related videos on Youtube

Mindaugas
Author by

Mindaugas

Updated on June 04, 2022

Comments

  • Mindaugas
    Mindaugas almost 2 years

    I have:

    <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1" />
    

    On validation in http://validator.w3.org/ I get this error:

    A meta element with an http-equiv attribute whose value is X-UA-Compatible must have a content attribute with the value IE=edge.

    I am working with .NET/Razor and of course locally using IIS. Is there a way to solve this without editing any web.config files? Thanks in forward.

    • Teemu
      Teemu over 9 years
      Why you want to add chrome=1 to the content?