- From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- Date: Mon, 30 Jan 2012 19:46:30 +0100
- To: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>
- Cc: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>, Andrew Fedoniouk <news@terrainformatica.com>, public-html@w3.org
Benjamin Hawkes-Lewis, Mon, 30 Jan 2012 18:24:46 +0000: > On Mon, Jan 30, 2012 at 8:06 AM, Leif Halvard Silli wrote: >>> Can you give an example of real content with inline-block tables? >> >> Example: The <object> element is supposed to be able to contain >> fallback for AT etc. And so, an image of a diagram could use a table >> as fallback. > > Can anyone give an example of real content where a diagram is inline > *and* the appropriate fallback would be a table? What does 'inline' mean? You pointed Andrew to HTML5, for another approach to what a 'paragraph' is. Well, anything inside a paragraph is inline. >>> What's your rationale for not using <div> instead of <p> here? >>> >>> Note how HTML5 defines what represents a "paragraph": >>> >>> http://dev.w3.org/html5/spec/content-models.html#paragraphs >> >> It is a bit unpractical to change the parent element just because the >> child element happens to to be an <object> with fallback, no? > > Aesthetically unpleasing, sure. But impractical? Likely not as > impractical as changing the parsing of <p>. You are wrong: It is not a parsing issue. The parsing handles this fine. It does not require any change of the HTML5 parser. It is solely a conformance issue. -- Leif Halvard Silli
Received on Monday, 30 January 2012 18:47:04 UTC