On Wed, Feb 17, 2010 at 8:03 AM, Simon St.Laurent <> wrote:
>
> The iframe element has always been a tricky critter, but in HTML5 it's
> picked up a srcdoc attribute which "gives the content of the page that the
> nested browsing context is to contain." This allows the construction of
> short documents in an iframe context without requiring a separate HTTP
> request through the src attribute.
>
<snip example/>
>
> What do folks think? Is this reasonable, given the use case, or is this
> pushing too hard on attributes and escaping?
>
> I wonder if just letting iframe have child content would make more sense,
> but I suspect that raises more compatibility problems with older browsers.
>
Man, that's _ugly_. I'd vote for just letting the iframe have child
content. As it sits, there is nothing stopping people from plopping
child content into an iframe with prior HTML versions and older
browsers; the older browsers have already got to be able to handle
child content in iframes, even if handling it means ignoring it....
--
Peter Hunsberger
