Re: [xml-dev] element markup in attributes
> I wonder if just letting iframe have child content would make more sense, but I suspect that raises more compatibility problems
> with older browsers.
Why not go with this more sensible option unless someone has a valid argument against it?
FWIW: IE6, IE8, FF3.6, Chrome 4.0 and Opera 10.10 all show the same behavior:
They hide the content of the <iframe> element and only show content for a document referenced with @src.
The same behavior you would expect when using @srcdoc.
I would expect the same behavior in older browsers as well, but I haven't confirmed.
Laurens van den Oever
Xopus BV
+31 70 4452345
KvK 27301795
2010/2/17 Simon St.Laurent <[email protected]>
I hesitate a bit in raising questions about HTML5 here, mostly because of concerns that the violence of that conversation will enter the discussion here. Nonetheless, this list is the best place I know of to discuss markup best practices, and seems like the right place to ask the question.
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.
Details can be found here:
<http://dev.w3.org/html5/spec-author-view/the-iframe-element.html>
<http://www.whatwg.org/specs/web-apps/current-work/multipage/the-iframe-element.html>
So what does this look like? Here are three examples from those specs.
-----------------------------------
<iframe seamless sandbox="allow-same-origin" srcdoc="<p>did you get a cover picture yet?"></iframe>
<iframe seamless sandbox="allow-same-origin" srcdoc="<p>Yeah, you can see it <a href="/gallery?mode=cover&amp;page=1">in my gallery</a>."></iframe>
<iframe seamless sandbox="allow-same-origin" srcdoc="<p>hey that's earl's table.
<p>you should get earl&amp;me on the next cover."></iframe>
-----------------------------------
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.
Thanks,
--
Simon St.Laurent
http://simonstl.com/
_______________________________________________________________________
XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.
[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: [email protected]
subscribe: [email protected]
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php