W3C home > Mailing lists > Public > public-html@w3.org > January 2012

Re: [Bug 15730] New: Suggestion: Introduce "content" element

From: Christopher Healey <deezignink@gmail.com>
Date: Fri, 27 Jan 2012 00:00:29 +0800
Cc: public-html@w3.org
Message-Id: <4F0B2595-3108-44A6-8E50-A1B7FE160054@gmail.com>
To: bugzilla@jessica.w3.org
We already have <article> and <section> what semantic addition could <content> bring that doesn't further obfuscate how a document should be read?


On Jan 26, 2012, at 11:47 PM, bugzilla@jessica.w3.org wrote:

> https://www.w3.org/Bugs/Public/show_bug.cgi?id=15730
> 
>           Summary: Suggestion: Introduce "content" element
>           Product: HTML WG
>           Version: unspecified
>          Platform: PC
>        OS/Version: Windows NT
>            Status: NEW
>          Severity: normal
>          Priority: P2
>         Component: HTML5 spec (editor: Ian Hickson)
>        AssignedTo: ian@hixie.ch
>        ReportedBy: ian.html@gmail.com
>         QAContact: public-html-bugzilla@w3.org
>                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
>                    public-html@w3.org
> 
> 
> 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.
> 
> -- 
> Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug.
> 
> 
> 
Received on Friday, 27 January 2012 22:06:11 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:29 UTC