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 9268 - Why can’t we just reuse the <caption> element and describe its meaning according to context? (i.e., spec gives directions for “caption in table” and “caption in figure” contexts.) Semantically, both fulfill the same purpose. And even if there
Summary: Why can’t we just reuse the <caption> element and describe its meaning accord...
Status: RESOLVED INVALID
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-18 15:04 UTC by contributor
Modified: 2010-10-04 14:45 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2010-03-18 15:04:12 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#the-figcaption-element

Comment:
Why can’t we just reuse the <caption> element and describe its meaning
according to context?  (i.e., spec gives directions for “caption in table”
and “caption in figure” contexts.)	Semantically, both fulfill the same
purpose.  And even if there are nuanced differences, it is not harder to grasp
than some of the other context-sensitive meanings in HTML5 (elements that
“reset the hierarchy”, for example.)

Posted from: 129.2.139.195
Comment 1 Ms2ger 2010-03-18 20:17:46 UTC 
Legacy parsing constraints. It would be impossible to use the figure element inside a table.