- From: <bugzilla@jessica.w3.org>
- Date: Wed, 26 Feb 2014 21:08:41 +0000
- To: www-validator-cvs@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24799
Michael[tm] Smith <mike@w3.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |mike@w3.org
Resolution|--- |WORKSFORME
--- Comment #1 from Michael[tm] Smith <mike@w3.org> ---
(In reply to Andrea Rendine from comment #0)
> The validator does not flag as incorrect markup present inside <title>,
> <textarea>
That's because inside those elements in text/html there is no such thing as
markup. Any characters that looks like markup within those elements are
actually just text.
> and presumably other text-content elements in HTML document, as
> expected by the spec.
No, what's expected by the spec is that all characters in those elements are
handled as text, not as markup.
> But it does flag them so in XHTML documents.
That's because in XML those characters that look like markup are in fact always
markup. So <title> and <textarea> in XML documents can't contain markup.
> Since the presence of markup inside these elements constitutes both a risk
> and a reason for different DOM trees in documents of either type, please
> correct it ASAP.
No, please read the spec more carefully and take time to actually understand
it.
The validator is following the spec here. So it sounds like you don't like the
behavior that the spec requires. Which is to say, you don't like the way that
browsers actually handle the contents of <title> and <textarea> elements.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 26 February 2014 21:08:43 UTC