Re: iframe@srcdoc

Last attempt to either have any attention to my proposal or to understand
why it is not viable. Hope that someone helps.
Summary of my previous mail:
1. The srcdoc attribute on iframe element is unconvenient:
 - it's complex to create any valuable script-generated content
 - it's complex to use for authors too, as it does not give access to
syntax highlighting or page validation and its content is visually messy.
 - is it's way too complex to parse, as it relies on double parsing
mechanism and the content must be passed as external document in a really
unnatural way.
 - It is theoretically absurd to pass markup as attribute value.
 - It is useless for data mining scripts and tools, which cannot develop a
separate parsing and document creation mechanism similar to user agents.
 - its support in XHTML is dubious, it almost entirely relies on the
complete support for "seamless" attribute for graphical layout.
 - and much more...
2. Why can't the same functionality be achieved using the content of the
iframe element? It'd be enough to extend the content model to "transparent"
(with the eventual exclusion of script elements for XHTML documents).

What the issues? Please advise.