This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Depending on outcome of Issue-100 and Issue-103, describe how to write make @srcdoc XML-compatible. Also see: http://www.w3.org/2002/09/wbs/40318/issue-103-objection-poll/results
Hi Leif. Sine these issues are now decided, can you be clear about what you are looking for? What do you want to see added? Is it just something about the way the attributes value is encoded, or is it making the document thats inside the sourcedoc an xml-compatible document? I'd appreciate it if you could propose text for any change required. Thanks, Eliot
The two issues mentioned in the original bug have been resolved. As such, I am resolving this bug as "needs info." Please indicate whether any action should be taken based on the decisions. If no action needs to be taken, the bug can remain resolved. Thanks, Eliot
HTML5 now says: http://dev.w3.org/html5/spec/the-iframe-element.html#process-the-iframe-attributes ]] Due to restrictions of the XML syntax, in XML the U+003C LESS-THAN SIGN character (<) needs to be escaped as well. In order to prevent attribute-value normalization, some of XML's whitespace characters specifically U+0009 CHARACTER TABULATION (HT), U+000A LINE FEED (LF), and U+000D CARRIAGE RETURN (CR) also need to be escaped. [XML] [[ Btw, this bug also directly relates to bug 9965. As such the issue could be seen as being covered by bug 9965. However, if you don't objecet, then I would suggest adding a note specifically about @srcdoc, as it is a very new, anti-pattern-ish attribute. May be you could solve this issue as part of solving bug 9965. That is, I think you could specifically mention @srcdoc under secftion 7: http://dev.w3.org/html5/html-xhtml-author-guide/html-xhtml-authoring-guide.html#attributes E.g. add, there, that escaping of tabs, line-feed and carriage-return is a particulary relevant with regard to @srcdoc. Either that or make separate in another place in the document.
I added the following example in section 7: Example <iframe srcdoc="<p>Hello 
 	 world!</p>" src="demo_iframe_srcdoc.htm"></iframe> I believe that this fulfills the requirements of this bug and so I have resolved it. Thanks for your help, Eliot
(In reply to comment #4) > Example > <iframe srcdoc="<p>Hello 
 	 world!</p>" > src="demo_iframe_srcdoc.htm"></iframe> Very good. I am satisfied. But you have forgotten to escape all the necessary characters: the '<' (Less than) sign occurs twice inside that @srcdoc attribute. And "<" must be escaped in XML.
Changed the example to the following: Example<iframe srcdoc="<p>Hello 
 	 world!</p>" src="demo_iframe_srcdoc.htm"></iframe> Thanks! Eliot
(In reply to comment #6) > Changed the example to the following: > > Example<iframe srcdoc="<p>Hello 
 	 world!</p>" > src="demo_iframe_srcdoc.htm"></iframe> Dear Eliot ... The point is to show what _needs_ to be escaped, and to leave everythingelse un-escaped, right? And - in fact - the ">" does _not_ need to be escaped. (And this is the reason why I did _not_ ask you to escape the ">" - I only asked you to escape the "<". I only asked you to escape the "<". So please revert the > to >.
Hi Leif. Reverted: ]] Example <iframe srcdoc="<p>Hello 
 	 world!</p>" src="demo_iframe_srcdoc.htm"></iframe> [[ Thanks for keeping me honest! Eliot
mass-move component to LC1