- From: Ian Hickson <ian@hixie.ch>
- Date: Wed, 20 Aug 2008 09:49:58 +0000 (UTC)
On Wed, 14 Mar 2007, Lachlan Hunt wrote: > > 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 > paragraphs. > > 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.) > > <header> > <h1><img src="/images/logo" alt="Company Name"></h1> > <object data="flash"></object> > </header> > > 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. This is all now allowed. On Tue, 13 Mar 2007, Andrew Fedoniouk wrote: > > I would add to the list also <select type="list">, <textarea>, > <richtext> - all active elements that are mutiline by their nature. This will be too. On Sun, 8 Apr 2007, Henri Sivonen wrote: > > It might make sense to allow <figure> as struct inline. The interaction > with <p> parsing in text/html would require research. On Sun, 8 Apr 2007, Henri Sivonen wrote: > > Anne says <figure> should work as a child of <p> as far as text/html > parsing goes. I'm not convinced that this is worth it. <figure> is basically a paragraph replacement, why would it be _in_ a paragraph? -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Wednesday, 20 August 2008 02:49:58 UTC