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 10080 - "in body" insertion mode, "any other end tag", step 2.2 seems wrong.
Summary: "in body" insertion mode, "any other end tag", step 2.2 seems wrong.
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P1 critical
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
: 10078 10079 (view as bug list)
Depends on: 10063
Blocks:
  Show dependency tree / graph
 
Reported: 2010-07-04 20:10 UTC by Eric Seidel
Modified: 2010-10-22 10:35 UTC (History)
8 users (show)

See Also:

Attachments

Description Eric Seidel 2010-07-04 20:10:42 UTC 
"in body" insertion mode, "any other end tag", step 2.2 seems wrong:

2. If node has the same tag name as the token, then:

2.1 Generate implied end tags.

2.2 If the tag name of the end tag token does not match the tag name of the current node, this is a parse error.

2.3 Pop all the nodes from the current node up to node, including node, then stop these steps.


2.2. should instruct implementors to abort the steps after the parse error, since reaching 2.3, having already popped the node in 2.1 will fail?
Comment 1 Simon Pieters 2010-07-05 14:02:18 UTC 
The steps shouldn't be aborted, but 2.1 should say to generate implied end tags except the tag name of the current token. I think jgraham has already filed a bug for that.
Comment 2 Eric Seidel 2010-07-09 06:40:09 UTC 
*** Bug 10078 has been marked as a duplicate of this bug. ***
Comment 3 Ian 'Hixie' Hickson 2010-07-14 19:14:33 UTC 
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: see diff given below
Rationale: Concurred with comment 1.
Comment 4 contributor 2010-07-14 19:14:55 UTC 
Checked in as WHATWG revision r5162.
Check-in comment: Change the 'end tag' processing to not imply its own end tag, since that makes no sense. (Only affects parsing of rp and rt elements.) Also clean up the way categories are references to avoid too many negatives, and put option and optgroup in the 'special' category (should have no effect in practice). And make a loop use a label rather than jumping to a numbered step.
http://html5.org/tools/web-apps-tracker?from=5161&to=5162
Comment 5 Ms2ger 2010-10-22 10:35:04 UTC 
*** Bug 10079 has been marked as a duplicate of this bug. ***