• From: cbullard@h...
• To: "Simon St.Laurent" <simonstl@s...>
• Date: Wed, 17 Feb 2010 08:54:51 -0600

Initially, I'd say bad practice but then why are they doing that?

On the other hand, there is the precedent of adding javascript via  
that trick.  There is also the precedent of older SGML proto XML  
systems such as IADS that put subcontent in frames in the war of  
cardsharks and holy scrollers.

On the other other hand, seems I've been reading that HTML5 is cutting  
the cord back to SGML and XML anyway meaning they're free to make up  
any parsing and escaping rules they care to make.  It's a top to  
bottom gencode approach.  Happy to be corrected if those assumptions  
are wrong.

len


Quoting "Simon St.Laurent" <simonstl@s...>:

> 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=&quot;/gallery?mode=cover&amp;amp;page=1&quot;>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;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: xml-dev-unsubscribe@l...
> subscribe: xml-dev-subscribe@l...
> List archive: http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>
>

• References:
  • element markup in attributes
    • From: "Simon St.Laurent" <simonstl@s...>