This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 14555 - Hi, I'd just like to understand why not using the already-defined "caption" tag, currently used only for tables, as a child of the new "figure" tag. Thanks.
Summary: Hi, I'd just like to understand why not using the already-defined "caption" t...
Status: RESOLVED WONTFIX
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-25 07:26 UTC by contributor
Modified: 2012-07-18 18:40 UTC (History)
2 users (show)

See Also:

Attachments

Description contributor 2011-10-25 07:26:20 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/grouping-content.html
Multipage: http://www.whatwg.org/C#the-figcaption-element
Complete: http://www.whatwg.org/c#the-figcaption-element

Comment:
Hi, I'd just like to understand why not using the already-defined "caption"
tag, currently used only for tables, as a child of the new "figure" tag.
Thanks.

Posted from: 109.9.172.77 by leandro.mattioli@gmail.com
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1
Comment 1 Ian 'Hixie' Hickson 2011-10-28 20:07:21 UTC 
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: I wanted to, or at least, failing that, <legend>, but it turns out the parsing behaviour around those elements makes them unusable in other contexts.