W3C home > Mailing lists > Public > www-validator-cvs@w3.org > August 2011

[Bug 11954] Validator should not return error for x-ua-compatible meta tag

From: <bugzilla@jessica.w3.org>
Date: Fri, 12 Aug 2011 14:27:16 +0000
To: www-validator-cvs@w3.org
Message-Id: <E1Qrshg-0008Di-4a@jessica.w3.org>

Marat Tanalin <mtanalin@yandex.ru> changed:

           What    |Removed                     |Added
                 CC|                            |mtanalin@yandex.ru

--- Comment #1 from Marat Tanalin <mtanalin@yandex.ru> 2011-08-12 14:27:13 UTC ---
Agreed. X-UA-Compatible meta element is REQUIRED to ensure that IE8+ user
cannot accidentally switch to harmful "Compatibility view" mode by accidental
pressing appropriate small graphic button in IE GUI.

This button gets hidden only when using "X-UA-Compatible" meta element with
"IE=edge" value sothat switching gets impossible. If button is not hidden and
is pressed by user, IE8/9 switches to operate as old IE7. This makes all the
web to stuck with old IE7 rendering and bugs even while users actually use
modern IE9.

Worse, this IE setting persists between browser sessions, so, once switched to
"Compatibility view" mode, the site will ALWAYS work as in IE7 for particular
user. Very often, users press the button ACCIDENTALLY, so the button should be
hidden anyway for any modern site -- by using X-UA-Compatible meta elements.
Returning named HTTP-response server header is not always possible, so the meta
element is (and definitely will be) widely used.

Moreover, before HTML5, this was not an error. HTML5 authors should not invent
such nonsensical limitations.


More generally -- it's not of HTML spec responsibility AT ALL to dictate what
meta elements are allowed and what are not.

Meta element should be considered valid if it conforms to general HTML syntax
as for tags and attributes, not particular values at all.

Meta element should be able to have any name ("name"/"http-equiv" attribute)
and any value ("content" attribute).

As a last resort, non-standard meta elements should be notices, not errors,
during validation. Considering these as errors is just detaching from reality.
Such detaching from reality is why XHTML1 has beed superceded with HTML, as
well as why XHTML2 has been dropped at all.

W3C should not make this mistake again. HTML spec should be free from such
redundant harmful limitations.


Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 12 August 2011 14:27:17 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:02:50 UTC