11045 2010-10-14 10:32:58 +0000 U+0020 does not need to be escaped in srcdoc in XML 2011-08-04 05:35:27 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified PC All CLOSED FIXED P2 normal --- 1 zcorpan ian ian julian.reschke mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 41350 0 zcorpan 2010-10-14 10:32:58 +0000 The new text for the Working Group Decision on ISSUE-103 srcdoc-xml-escaping says that U+0020 needs to be escaped. Due to restrictions of the XML syntax, - in XML a number of other characters need to be escaped also to - ensure correctness. + in XML the U+003C LESS-THAN SIGN character (<) needs to be + escaped as well. In order to prevent <a + href="http://www.w3.org/TR/REC-xml/#AVNormalize">attribute-value + normalization</a>, XML's whitespace characters — U+0009 + CHARACTER TABULATION (HT), U+000A LINE FEED (LF), U+000D CARRIAGE + RETURN (CR) and U+0020 SPACE — also need to be escaped. <a + href="#refsXML">[XML]</a> My reading of the XML spec suggests space does not need to be escaped. http://www.w3.org/TR/REC-xml/#AVNormalize "For a white space character (#x20, #xD, #xA, #x9), append a space character (#x20) to the normalized value." i.e. a literal space and an escaped space results in the same thing. The paragraph "If the attribute type is not CDATA, then the XML processor MUST further process the normalized attribute value by discarding any leading and trailing space (#x20) characters, and by replacing sequences of space (#x20) characters by a single space (#x20) character." does not apply since srcdoc is a CDATA attribute (and none of the allowed doctypes change that for srcdoc even if the UA uses a validating processor). 41351 1 zcorpan 2010-10-14 10:35:28 +0000 Hmm, actually HTML5 allows any doctype in XML, so that paragraph *could* apply if the author goes out of his way to change srcdoc to be something other than CDATA, but in that case we could assume that the author knows what he's doing and the note doesn't need to cover that case IMHO. 43546 2 ian 2010-12-26 19:58:14 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: If you disagree with the decision, please use the WG process to handle it. I'm not going to change the text without instruction from the chairs, especially on this issue, where my whole objection to the issue in the first place was that adding this text would mean it would be micromanaged for months afterwards. 43559 3 zcorpan 2010-12-27 09:27:45 +0000 > If you disagree with the decision, please use the WG process to handle it. I don't disagree with the decision. I'm following the WG process here. http://lists.w3.org/Archives/Public/public-html/2010Oct/0211.html 44249 4 ian 2011-01-11 23:32:46 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments. 44251 5 contributor 2011-01-11 23:39:41 +0000 Checked in as WHATWG revision r5777. Check-in comment: this paragraph really shouldn't be in the spec in the first place, but since it's there, let's at least make it mostly correct http://html5.org/tools/web-apps-tracker?from=5776&to=5777 54026 6 mike 2011-08-04 05:35:27 +0000 mass-move component to LC1