- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 29 Jan 2008 13:41:45 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5439 Summary: [SER] include-content-type HTML vs. XHTML Product: XPath / XQuery / XSLT Version: Recommendation Platform: PC OS/Version: Windows NT Status: NEW Severity: normal Priority: P2 Component: Serialization AssignedTo: zongaro@ca.ibm.com ReportedBy: tim@cbcl.co.uk QAContact: public-qt-comments@w3.org When include-content-type is "yes" and a meta element has been added to the head element, should the conditions for stripping out existing meta element differ between HTML and XHTML. If so, why? 6.1.13 XHTML Output Method: the include-content-type Parameter If a meta element has been added to the head element as described above, then any existing meta element child of the head element having an http-equiv attribute with the value "Content-Type", making the comparison without consideration of casing and leading/trailing spaces, MUST be discarded. 7.4.13 HTML Output Method: the include-content-type Parameter "If a meta element has been added to the head element as described above, then any existing meta element child of the head element having an http-equiv attribute with the value "Content-Type" MUST be discarded."
Received on Tuesday, 29 January 2008 13:41:51 UTC