Open Jayman2000 opened 3 years ago
According to the HTML Standard, a meta element can have its http-equiv attribute set to content-type. In this situation, the http-equiv attribute is in the Encoding declaration state. The proposed CC0 1.1 has an http-equiv attribute that’s in the Encoding declaration state.
meta
http-equiv
content-type
<meta http-equiv="content-type" content= "text/html; charset=utf-8" />
According to the HTML Standard, “The Encoding declaration state may be used in HTML documents, but elements with an http-equiv attribute in that state must not be used in XML documents.” The proposed CC0 1.1 is an XML document.
.xht
.xhtml
The page validates successfully.
I would be interested in resolving this bug.
Description
According to the HTML Standard, a
meta
element can have itshttp-equiv
attribute set tocontent-type
. In this situation, thehttp-equiv
attribute is in the Encoding declaration state. The proposed CC0 1.1 has anhttp-equiv
attribute that’s in the Encoding declaration state.According to the HTML Standard, “The Encoding declaration state may be used in HTML documents, but elements with an
http-equiv
attribute in that state must not be used in XML documents.” The proposed CC0 1.1 is an XML document.Reproduction
.xht
or.xhtml
.Expectation
The page validates successfully.
Resolution