W3C home > Mailing lists > Public > public-html@w3.org > August 2011

Re: <caption>, <figcaption>, <seccaption>, <divcaption>, etc.

From: Simon Pieters <simonp@opera.com>
Date: Mon, 29 Aug 2011 07:02:23 +0200
To: "Leif Halvard Silli" <xn--mlform-iua@xn--mlform-iua.no>, "Andrew Fedoniouk" <news@terrainformatica.com>, "Andrew Fedoniouk" <andrew.fedoniouk@live.com>
Cc: public-html@w3.org
Message-ID: <op.v0yll9bfidj3kv@simon-pieterss-macbook.local>
On Sun, 28 Aug 2011 22:21:40 +0200, Andrew Fedoniouk  
<andrew.fedoniouk@live.com> wrote:

> To be honest I do not understand the idea of such reasoning.
>
> Say if in HTML5 we will decide to always parse <caption>
> as such a <span> element: <body>
>   <caption>Caption text</caption> </body>
>
> will be parsed and create DOM of this structure
> <body>
>   <caption style="display:inline">Caption text</caption> </body>
>
> Currently HTML parsers create just this for some reason:
> <body>
>   Caption text
> </body>
>
> These two cases are undistinguishable for the human - so the solution is  
> backward compatible. I don't think we can
> find existing markup on the web that relies on the fact that <caption>
> and </caption> tags are silently ignored by modern browsers.

If you looked more closely at the resulting DOM in

>>>>  http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1122

you would notice that parsing of caption is far more problematic when  
found inside a table cell.

And yes, this has been discussed to death several times. :-)

-- 
Simon Pieters
Opera Software
Received on Monday, 29 August 2011 05:02:52 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:37 GMT