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 14521 - Why does <fieldset> have <legend> but <table> have <caption> ? I think they both ought to use either <legend> or <caption>. This would eliminate a tag and reduce complexity. Both <legend> and <caption> are basically the same thing anyways?
Summary: Why does <fieldset> have <legend> but <table> have <caption> ? I think they b...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
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: 2011-10-20 10:01 UTC by contributor
Modified: 2011-10-20 10:08 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2011-10-20 10:01:18 UTC 
Specification: http://dev.w3.org/html5/spec/
Multipage: http://www.whatwg.org/C#top
Complete: http://www.whatwg.org/c#top

Comment:
Why does <fieldset> have <legend> but <table> have <caption> ?

I think they both ought to use either <legend> or <caption>.
This would eliminate a tag and reduce complexity.

Both <legend> and <caption> are basically the same thing anyways?

Posted from: 212.247.162.243
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1
Comment 1 Simon Pieters 2011-10-20 10:08:02 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: We can't change this because it would break the web.