[Bug 11256] New: Obtaining correct outline when article is entire body of document X


           Summary: Obtaining correct outline when article is entire body
                    of document  X
           Product: HTML WG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P3
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: jjc@jclark.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,

The HTML5 <article> element seems potentially very useful, but there
seems to me to be an aspect of the overall design that makes it work
not quite as well as it might.

I'm guessing that HTML5 is designed to support the scenario where an
author creates create potentially reusable chunks of HTML5 content,
which are then assembled by the publishing system into valid HTML5
documents, where these reusable chunks would typically use <article>
or <section> as their root element.  The problem with the current
design seems to me to occur when you want such a chunk to be the
entire content of a page.  I don't see any way to get the "right"
outline without modifying the reusable chunk. If I simply wrap the
<article> in a <body> in the obvious way:

<h1>Article title</h1>

then I get an outline, according to [1], where the <body> node is a
section with an implied heading containing a single section with a
"Article title" heading, whereas I would want to get the same outline

<h1>Article title</h1>

One way round this might be a "nosection" boolean attribute on <body>,
which would say to the outline algorithm not to create a section for
the <body> element, and which would be valid only when the <body>
element consists of a single sectioning content element.

[1] http://dev.w3.org/html5/spec/Overview.html#outlines

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 Monday, 8 November 2010 09:13:29 UTC