[whatwg] Embedding Elements Should be Structured Inline-Level

Lachlan Hunt lachlan.hunt at lachy.id.au
Tue Mar 13 22:23:47 PDT 2007

   The spec currently defines most embedding elements (img, iframe, 
embed, object, video and canvas) as strictly inline level and thus only 
allows them to be used in contexts where strictly inline level content 
may be used.

I think these elements should be defined as structured inline-level 
elements.  When used in block level contexts, they should represent 

The specific use case I have come across which requires this is 
something like the following.  (Although, the site I'm currently 
building is HTML4 and using <div id="header"> instead.)

     <h1><img src="/images/logo" alt="Company Name"></h1>
     <object data="flash"></object>

In this particular case, it doesn't make sense to add an extra <p> or 
<div> around the object just to get around the contextual usage restriction.

HTML4 currently allows object and iframe to be used where block level 
elements are allowed, and I don't think HTML5 should restrict that.

Lachlan Hunt

More information about the whatwg mailing list