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

[Bug 24799] Text-content elements in HTML

From: <bugzilla@jessica.w3.org>
Date: Wed, 26 Feb 2014 21:23:54 +0000
To: www-validator-cvs@w3.org
Message-ID: <bug-24799-169-FaVeaD8DDY@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24799

--- Comment #2 from Andrea Rendine <master.skywalker.88@gmail.com> ---
I have read and understood clearly the spec, but thank you for your kind
proposal.

Thus said, there is a slight difference in meaning between
[[The HTML parser treats markup inside iframe elements as text.]](iframe)
which EXPLICITLY states the behavior of UAs in regard to an element whose
content is considered text no matter what characters are used, and
[[The IDL attribute text must return a concatenation of the contents of all the
Text nodes that are children of the title element (ignoring any other nodes
such as comments *or elements*), in tree order. On setting, it must act the
same way as the textContent IDL attribute.]](title)

If you are right, then tell me what kind of element could ever be inside
<title>. Or <textarea>, for what is the matter.
Or the 'text' IDL attribute is required to return something different than the
actual title of the document (i.e. the one shown in the browser's window/tab)?
First off, the browsers' 'text' IDL attribute implementation does not seem to
honour the requested behaviour. Or the sentence "Text nodes that are children
of the title element (ignoring any other nodes such as comments *or elements*)"
is meant to be completed with the sentence "actually everything inside a
<title> is text, except for comments (but it is not stated)".

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 26 February 2014 21:23:55 UTC

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