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

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

From: Andrew Fedoniouk <andrew.fedoniouk@live.com>
Date: Sun, 28 Aug 2011 13:21:40 -0700
Message-ID: <BLU165-ds120F6B1BF94A18CCF8B118F8150@phx.gbl>
To: "Leif Halvard Silli" <xn--mlform-iua@xn--mlform-iua.no>, "Andrew Fedoniouk" <news@terrainformatica.com>
Cc: <public-html@w3.org>, "Simon Pieters" <simonp@opera.com>
-----Original Message----- 
From: Leif Halvard Silli 
Sent: Friday, August 26, 2011 10:11 AM 
To: Andrew Fedoniouk 
Cc: public-html@w3.org ; Simon Pieters 
Subject: Re: , , , , etc. 

>Andrew Fedoniouk, Fri, 26 Aug 2011 08:18:57 -0700:
>> Sent: Friday, August 26, 2011 3:14 AM
>>> On Fri, 26 Aug 2011 06:17:21 +0200, Andrew Fedoniouk wrote:
>
>>>> caption { display:block; }
>>>> table > caption { display:table-caption; }
>    ...
>>>> My pardon if it was discussed already.
>>> 
>>> http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1122
>
>> http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1123
>  ...
>> As you see <legend> is parsed in even it is used outside of
>> <fieldset> but <caption> for some reason is simply ignored.
>> Very strange logic to be honest.
>
>Sometimes I regret that we problematisized the <legend/> element: [1]
>
>]]
>  * The figure element now uses a new element figcaption rather
>    than legend because people want to use HTML5 long before it
>    reaches W3C Recommendation.
>  * The details element now uses a new element summary for exactly
>    the same reason.
>[[
>
>But as your example code shows: Had we choosen <caption/> rather than 
><figcaption/> and <summary/>, the time before people could use 
><figure/> and <details/> would probably have been prolonged rather than 
>diminished. 
>[1] http://www.w3.org/TR/html5-diff/#changes-2009-08-25
>-- 

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.

-- 
Andrew Fedoniouk

http://terrainformatica.com
Received on Sunday, 28 August 2011 20:22:09 GMT

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