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 15730 - Suggestion: Introduce "content" element
Summary: Suggestion: Introduce "content" element
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Edward O'Connor
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-26 15:47 UTC by Ian Yang
Modified: 2012-09-06 18:27 UTC (History)
5 users (show)

See Also:


Attachments

Description Ian Yang 2012-01-26 15:47:01 UTC
While coding for the content of a blog post, we have <header> to wrap heading, author, and publish time; And we have <footer> to wrap categories links and other metadata; However, we currently don't have <content> to wrap paragraphs and figures.

Therefore, maybe we could have <content> introduced.
Comment 1 Ian Devlin 2012-01-26 16:03:25 UTC
But there are the <section> and <article> elements available to wrap such things? If you have a <header>, <footer> and several <aside>s in an <article> or <section>, than everything else IS content. Process of elimination.
Comment 2 Ian Yang 2012-01-26 16:36:28 UTC
(In reply to comment #1)
> But there are the <section> and <article> elements available to wrap such
> things? If you have a <header>, <footer> and several <aside>s in an <article>
> or <section>, than everything else IS content. Process of elimination.

Process of elimination is okay. However, without being wrapped by a <content> tag, all content elements look like they are at the same level as <header> and <footer> elements.

If we have the <content> tag to wrap all those various content elements, our mockup will looks cleaner and tidier.
Comment 3 contributor 2012-07-18 06:54:53 UTC
This bug was cloned to create bug 17819 as part of operation convergence.
Comment 4 Edward O'Connor 2012-09-06 18:27:18 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 change.

Rationale: This has been considered and rejected several times in the
history of this WG. For instance, see this thread from August 2009:

http://lists.w3.org/Archives/Public/public-html/2009Aug/thread.html#msg858

Feel free to repoen this bug if you have new information.