W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > March 2010

[Bug 7056] <caption> and <figure><legend> elements should allow flow content children

From: <bugzilla@wiggum.w3.org>
Date: Mon, 15 Mar 2010 12:03:14 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Nr90s-0002H2-MC@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7056





--- Comment #12 from Maciej Stachowiak <mjs@apple.com>  2010-03-15 12:03:14 ---
(In reply to comment #11)
> Discussed in February 2009: The need to separate table title from table info
> data. Here is Ian's reply:
> 
> http://lists.w3.org/Archives/Public/public-html/2009Feb/0690
> 
> On Tue, 24 Feb 2009, Leif Halvard Silli wrote:
> >> 
> >> Explanation: One only needs to read the table instruction as long as one 
> >> is unfamilar with the table. Once one is familar with the table (because 
> >> one has gone through it in all directions oneself) one will not be so 
> >> interested the overview anymore.
> >> 
> >> So, it is not that the caption becomes more important, perhaps, but the 
> >> summary that becomes less important. (It could als also be the opposite 
> >> though: As you becomes familiar with the table, you understand the 
> >> overview better.)
> >> 
> >> This is also one reason that one needs to distinguish captioning content 
> >> from summarising content. One must be able to know what one refers to.
> >
> >Why?
> >
> >Consider the example in the spec, with the table for dice. Why wouldn't a 
> >user just learn to ignore the caption once they knew what it said, 
> >skipping past it to the table content? How would the UI be any different 
> >if the user agent knew that the table's name ended at one point and the 
> >usage help started after that point? Surely the user would still just have 
> >to hit the "advance to next block" key either
> 

It seems to me that the request for a special element to set apart some or all
of the caption is a wholly separate request from this bug.

The request in this bug was to allow <caption> to contain flow content instead
of just phrasing content. The upshot of that is that <caption> is now allowed
to contain block-level elements. It seems to me that we would not want to
remove that capability even if we had a mechanism to structure the caption's
contents.



-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 15 March 2010 12:03:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 15 March 2010 12:03:21 GMT