[Bug 11198] New: Heading structure(h1-h6) rigidity makes it very hard to reuse content


           Summary: Heading structure(h1-h6) rigidity makes it very hard
                    to reuse content
           Product: HTML WG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: laurent.goderre@gmail.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,

Very often in working with complex web sites, I had to reuse parts of content
in multiple pages. If that content has its own heading structure, chances are
that including that content to another page will break the heading structure.

For example, if the main page has displays searches for two different major
categories of the site and on submitting a search, it goes to a separate page
for the results. That result page most likely contains the same form to do
another search if the results don't match what the user is looking for. On the
home page, the heading would have to be an h2 or lower under the Home Page h1
but on it's own page, it should be an h1. Another example is a complex policy
or standard document that is displayed both a multiple document set or a long
single document. Having a dynamic way of dealing with headings would allow to
maintain only one instance (the multiple set one) and have the long single one
refrence the pieces.

With the new 'section' element, there would be no need for an numbered heading.
If section were mandatory and not implied anymore, there could be a single
element to deal with all headings. As it is the case with fieldset, the first
element of a section could be a heading element defining the title of that

I understand it would be a bit more CSS (instead of h3 it would be section
section section heading {}) but it would create a more compliant structure for
complex data.

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, 2 November 2010 18:00:21 UTC