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

[Bug 11466] Reword 4.4.7 The hgroup element

From: <bugzilla@jessica.w3.org>
Date: Tue, 11 Jan 2011 00:51:05 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1PcSS1-0001BX-LV@jessica.w3.org>

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
                 CC|                            |ian@hixie.ch
         Resolution|                            |WONTFIX

--- Comment #3 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-01-11 00:51:04 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:

Status: Rejected
Change Description: no spec change
Rationale: I think it's too late to make a change of this nature without a very
compelling rationale. While it's true that public-html has been discussing
<hgroup> for a few weeks, there aren't that many participants in the
discussion, and the discussion seems to be primarily focused around people
thinking other people might not understand the feature, rather than people
themselves not understanding the feature. Such anecdotal  or even hypothetical
 confusion is not especially compelling at this stage: since the element has
been described in detail on many tutorial sites, in books, and so forth, we
would have to have very clear evidence of confusion before changing it.

In particular, I do not believe renaming <hgroup> to <hblock> is a perceptible

Other suggestions are to change the structure, e.g. to use a subelement of <h1>
to indicate a subheading, but I believe such suggestions ignore a core
principle of our work, sometimes referred to as "pave the cowpaths": in
practice, when people have a heading and a subheading, they just use different
levels of <hx>, and so it makes imminent sense to leverage that technique.

Dropping the feature altogether would harm accessibility (without this element,
the document outlines of documents with subheadings have spurious sections), so
I don't think that's a good idea either.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 11 January 2011 00:51:07 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:03 UTC