W3C home > Mailing lists > Public > www-validator-cvs@w3.org > March 2014

[Bug 25104] The RelaxNG schema should recognize more encoding values for the <annotation-xml> element

From: <bugzilla@jessica.w3.org>
Date: Mon, 24 Mar 2014 17:56:08 +0000
To: www-validator-cvs@w3.org
Message-ID: <bug-25104-169-JNf9irJANA@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25104

--- Comment #9 from Michael[tm] Smith <mike@w3.org> ---
(In reply to fred.wang from comment #0)
> The HTML5 RelaxNG schema currently allows the following values for the
> encoding attribute of the <semantics> element:
> 
> HTML => string "application/xhtml+xml" | string "text/html"

(In reply to David Carlisle from comment #8)
> However it is still basically true that in text/html there are only really
> two useful values for encoding, text/html and application/xhtml+xml. Any
> other value has the same effect as not having the encoding attribute at all.

So yeah the HTML parser depends on looking for those specific values for the
"encoding" attribute.

http://www.whatwg.org/specs/web-apps/current-work/multipage/tree-construction.html#html-integration-point

That part of the HTML spec says:

— A node is an HTML integration point if it is one of the following elements:

— An annotation-xml element in the MathML namespace whose start tag token had
an attribute with the name "encoding" whose value was an ASCII case-insensitive
match for the string "text/html"
— An annotation-xml element in the MathML namespace whose start tag token had
an attribute with the name "encoding" whose value was an ASCII case-insensitive
match for the string "application/xhtml+xml"

Then there are other parts of the spec that say what to do when you an "HTML
integration point" is encountered; e.g.:

 
http://www.whatwg.org/specs/web-apps/current-work/multipage/tree-construction.html#parsing-main-inforeign

—Pop an element from the stack of open elements, and then keep popping more
elements from the stack of open elements until the current node is a MathML
text integration point, an HTML integration point, or an element in the HTML
namespace.

So as far as I can see, the validator is aligned with the HTML spec here. If
you want something other than encoding=application/xhtml+xml or
encoding=text/html to be supported then you need to file a bug against the HTML
spec.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 24 March 2014 17:56:09 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:17:56 UTC