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:19:23 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Nr9GV-0003nW-CE@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7056





--- Comment #14 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>  2010-03-15 12:19:22 ---
(In reply to comment #12)
> (In reply to comment #11)
> > Discussed in February 2009: The need to separate table title from table info

> 
> 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.

Firstly: Ian has never commented this bug. Have you thought abvout why? I think
it is because he had already allowed what James asked for when James filed this
bug. (Compare the dates.). From that point of view, James's bug report may have
been invalid. I don't know why James filed it - perhaps because Ian's change
wasn't reflected in Validator.nu? I don't know. But since he has filed a bug
suggesting that <caption> should allow flow-content, it should not be necessary
to file a separate bug saying that it should not.

The points I want to make are: 

a) the content model of <caption> is not solved until @summary is solved. This
has been clear from the very start, when Ian started to allow any kind of table
info inside <caption>. (I say "any kind" in the sense "not only summaries for
non-visual media") 

b) <caption> has a role of its own. It is for table identification. At least so
it is in HTML4. We should be absolutely certain about the accessibility story
before watering out its role. We would not allow flow content inside <h1>. So
why inside <caption>?

c) <tableinfo> is just *one* possible solution to the problem - it is as
solution *if* flow content should go into <caption> - if there are enough
benefits for something like that.

Finally, may I ask: What is the justification for allowing flow content inside
<caption>?  James did not provide any. What is your justification, for example? 


-- 
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:19:26 GMT

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