[Bug 7527] Allow implementations to generate meaningful default, implied headings for some sections.

http://www.w3.org/Bugs/Public/show_bug.cgi?id=7527





--- Comment #2 from Lachlan Hunt <lachlan.hunt@lachy.id.au>  2009-09-07 13:14:21 ---
The current algorithm doesn't handle this case very intuitively:

<section>
  <p>Lots of introductory content...
  <section>
    <h1>Heading A</h1>
    <p>Now a subsection>
  </section>
  <h1>Heading B</h1>
  <p>And a new section
</section>


This currently generates an outline like:

+--Heading B
   |
   +--Heading A

This is unintuitive because the source order puts heading B after the section
with heading A, so it doesn't make sense that Heading B is placed structurally
above heading A.  This mismatch between source order and heading outline would
be confusing in, for example, a generated table of contents.

Intuitively, the outline should look equivalent to that generated by this:

<section>
  <p>Lots of introductory content...
  <section>
    <h1>Heading A</h1>
    <p>Now a subsection>
  </section>
</section>
<section>
  <h1>Heading B</h1>
  <p>And a new section
</section>

Which results in the outline like this:


+--[Untitled Section]
|  |
|  +--Heading A
|
+--Heading B

To handle this case more effectively, the algorithm should be modified in the
following way:

When entering a sectioning content element or a sectioning root element

--> If current outlinee is not null:
    * If current section does not have a heading, generate a default implied
      heading for the section.
      (e.g. "Navigation" for <nav>, "Article" for <article>, etc. [1])
    * push current outlinee onto the stack.

--> (leave the rest of these steps as is)

[1] The exact text for the default heading is not important. It should probably
be based on factors like the user's native language or whatever language is
supported by the tool, and be appropriate for the context in which it will be
used.  Maybe it could even be based on the sectioning element's title attribute
if it has one, or some other information available in the context.


-- 
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, 7 September 2009 13:14:30 UTC