15670 2012-01-22 17:19:03 +0000 Specify the behavior when a dangling <section> is encountered. 2012-08-10 03:06:03 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#outline P3 normal Unsorted 1 contributor ian ian kennyluck mike contributor oldest_to_newest 62987 0 contributor 2012-01-22 17:19:03 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/sections.html#the-nav-element Multipage: http://www.whatwg.org/C#outline Complete: http://www.whatwg.org/c#outline Comment: Specify the behavior when a dangling <section> is encountered. Posted from: 114.43.116.53 by kennyluck@csail.mit.edu 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 62988 1 kennyluck 2012-01-22 17:30:39 +0000 Consider <section> <!-- first --> <section></section> <!-- second --> <h1></h1> </section> , 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. 70470 2 contributor 2012-07-18 08:00:03 +0000 This bug was cloned to create bug 18004 as part of operation convergence. 72008 3 contributor 2012-08-10 03:06:03 +0000 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... http://html5.org/tools/web-apps-tracker?from=7240&to=7241