This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 15670 - Specify the behavior when a dangling <section> is encountered.
Summary: Specify the behavior when a dangling <section> is encountered.
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
Depends on:
Reported: 2012-01-22 17:19 UTC by contributor
Modified: 2012-08-10 03:06 UTC (History)
3 users (show)

See Also:


Description contributor 2012-01-22 17:19:03 UTC

Specify the behavior when a dangling <section> is encountered.

Posted from: by
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/534.51.22 (KHTML, like Gecko) Version/5.1.1 Safari/534.51.22
Comment 1 Kang-Hao (Kenny) Lu 2012-01-22 17:30:39 UTC

<section> <!-- first -->
   <section></section> <!-- second -->

, at the time when the algorithm walk in <h1>, the current section is the first <section> but now it gets an implied heading because of the second <second>, prose like

  # Otherwise, if the element being entered has a rank equal to or greater
  # than the heading of the last section of the outline of the current outlinee

is no longer well defined. Also, the second section never gets an implied heading. 

If you intend to leave this behavior undefined at the moment, I think you should just say so.
Comment 2 contributor 2012-07-18 08:00:03 UTC
This bug was cloned to create bug 18004 as part of operation convergence.
Comment 3 contributor 2012-08-10 03:06:03 UTC
Checked in as WHATWG revision r7241.
Check-in comment: Make the outline algorithm handle implied headings better. Really this should just be rewritten to be clearer...