24799 2014-02-25 13:08:18 +0000 Text-content elements in HTML 2014-02-26 21:43:46 +0000 1 1 1 Unclassified HTML Checker General unspecified PC Windows NT RESOLVED WORKSFORME P2 normal --- 1 master.skywalker.88 mike+validator master.skywalker.88 mike www-validator-cvs oldest_to_newest 101329 0 master.skywalker.88 2014-02-25 13:08:18 +0000 The validator does not flag as incorrect markup present inside <title>, <textarea> and presumably other text-content elements in HTML document, as expected by the spec. But it does flag them so in XHTML documents. 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. 101455 1 mike 2014-02-26 21:08:41 +0000 (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. 101459 2 master.skywalker.88 2014-02-26 21:23:54 +0000 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)". 101464 3 mike 2014-02-26 21:37:33 +0000 (In reply to Andrea Rendine from comment #2) > [[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) What possible relevance does that have to the behavior of the validator? When you give a document to the validator to check, it is impossible for that document to ever have a title element that contains any child elements. > If you are right, then tell me what kind of element could ever be inside > <title>. Or <textarea>, for what is the matter. You filed this bug against the validator. That question has zero relevance to the behavior of the validator. If you're curious about it, file a bug against the spec or something. For the purposes of documents you check with the validator, the no elements can ever be a child of <title> or <textarea>. Again the statement you cite above has absolutely no relevance to the behavior of the validator. So I don't know why you want to continue a discussion about this here. > 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)". Again, you filed this bug report against the validator. But I've told you already there's no bug in the validator here. So at this point I have no idea what else you expect me to do in response to this. 101467 4 master.skywalker.88 2014-02-26 21:43:46 +0000 So there are "elements in <title> for the purpose of IDL" and "elements in <title> for the purpose of validation". I see. I thought that elements are elements for every purpose. And that elements were not allowed in <title> for any purpose. Got it, I'll refer to the spec.