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 5858 - Case marked as fragment when it can occur at other times
Summary: Case marked as fragment when it can occur at other times
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Keywords: NoReply
Depends on:
Reported: 2008-07-11 20:59 UTC by Andrew Sidwell
Modified: 2010-10-04 14:57 UTC (History)
3 users (show)

See Also:


Description Andrew Sidwell 2008-07-11 20:59:11 UTC
The document "<!DOCTYPE><html><frameset></frameset></html></frameset>" results in the HTML element being the current element in the "in frameset" insertion mode even though this is not "(fragment case)", which is contrary to what the spec says.

After the first </frameset> tag, the current node is the html element; then the </html> tag moves to the "after after frameset" mode, where another </frameset> tag switches back to "in frameset" and tries to pop the current node, now the html element.

I would suggest just removing (fragment case), since that's what I've implemented.
Comment 1 Ian 'Hixie' Hickson 2008-07-23 02:33:44 UTC
...while I'm at it, I should make sure these get treated the same (right now they don't):

Comment 2 Ian 'Hixie' Hickson 2008-07-23 07:41:59 UTC
This ended up being a bigger problem, actually. Fixed.
Comment 3 Maciej Stachowiak 2010-03-14 13:15:12 UTC
This bug predates the HTML Working Group Decision Policy.

If you are satisfied with the resolution of this bug, 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:

This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment.