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 6038 - "noframes", "script", "style", "title" in 'after head' mode pop prematurely
Summary: "noframes", "script", "style", "title" in 'after head' mode pop prematurely
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Keywords: NoReply
Depends on:
Reported: 2008-09-08 10:03 UTC by Henri Sivonen
Modified: 2010-10-04 14:31 UTC (History)
4 users (show)

See Also:


Description Henri Sivonen 2008-09-08 10:03:03 UTC
Now that the tree builder is specified to be purely tokenizer push as opposed to being tree builder pull at times, the steps for "noframes", "script", "style", "title" in after head aren't quite right.

The steps involve popping the current node (claimed to be head) off the stack as the last step. However, the actions of the previous step have now changed, so this no longer makes sense (the current node won't be head and popping at this stage no longer makes sense).

Possible fixes:
 * Make </head> not pop head, so space characters, comments and "base", "link", "meta", "noframes", "script", "style", "title" after </head> simply get appended to head.
 * Make "noframes", "script", "style", "title" set a flag that tells the end tag processing for those pop an extra time. (This is what the HTML Parser already does.)
Comment 1 Henri Sivonen 2008-09-08 10:08:11 UTC
No need for a new flag. Just a test if original mode is 'after head'.
Comment 2 Tommy Thorsen 2008-11-11 14:12:43 UTC
A third possible solution may be to remove the head element from the stack instead of popping it.
Comment 3 Ian 'Hixie' Hickson 2008-12-02 03:59:26 UTC
Did the last option.
Comment 4 Maciej Stachowiak 2010-03-14 13:15:42 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.