18004 2012-07-18 08:00:00 +0000 Specify the behavior when a dangling <section> is encountered. 2012-09-14 05:11:54 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#outline P3 normal --- 1 contributor erika.doyle kennyluck mike public-html-admin public-html-wg-issue-tracking silviapfeiffer1 public-html-bugzilla oldest_to_newest 70469 0 contributor 2012-07-18 08:00:00 +0000 This was was cloned from bug 15670 as part of operation convergence. Originally filed: 2012-01-22 17:19:00 +0000 ================================================================================ #0 contributor@whatwg.org 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 ================================================================================ #1 Kang-Hao (Kenny) Lu 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. ================================================================================ 73842 1 silviapfeiffer1 2012-09-14 05:11:54 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: https://github.com/w3c/html/commit/2d4096f960a3a0de3562c9c93746336cafcef159 Rationale: accepted WHATWG fix