28227 2015-03-16 13:37:31 +0000 Shouldn't srcdoc in XHTML be parsed as XML, since the authoring requirements require the value to be XML? 2015-09-01 15:14:10 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED MOVED https://html.spec.whatwg.org/#process-the-iframe-attributes P3 normal Unsorted 1 contributor ian annevk ian mike zcorpan contributor oldest_to_newest 118622 0 contributor 2015-03-16 13:37:31 +0000 Specification: https://html.spec.whatwg.org/multipage/embedded-content.html Multipage: https://html.spec.whatwg.org/multipage/#process-the-iframe-attributes Complete: https://html.spec.whatwg.org/#process-the-iframe-attributes Referrer: https://html.spec.whatwg.org/multipage/ Comment: Shouldn't srcdoc in XHTML be parsed as XML, since the authoring requirements require the value to be XML? <http://www.w3.org/mid/550315FA.50400@mit.edu> Posted from: 212.247.211.200 by simonp@opera.com User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.74 Safari/537.36 OPR/28.0.1750.36 (Edition beta) 119101 1 ian 2015-03-30 23:15:57 +0000 Interesting. Good question. Dunno. Definitely the two should be consistent, but which should it be? 119144 2 zcorpan 2015-03-31 14:47:38 +0000 It seems the spec has been like this since srcdoc was first added. https://html5.org/r/4619 Current implementations parse as HTML. http://software.hixie.ch/utilities/js/live-dom-viewer/saved/3476 innerHTML uses XML parsing in XML documents. I don't have a strong opinion either way. I would have expected XML parsing, though. 122984 3 annevk 2015-09-01 15:14:10 +0000 https://github.com/whatwg/html/pull/77