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 6390 - Add a note about reaching after head state and the fragment mode
Summary: Add a note about reaching after head state and the fragment mode
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: 2009-01-13 17:47 UTC by Henri Sivonen
Modified: 2010-10-04 13:58 UTC (History)
3 users (show)

See Also:


Description Henri Sivonen 2009-01-13 17:47:25 UTC
In after head state, there's this:
"Push the node pointed to by the head element pointer onto the stack of open elements."

The possibility of the pointer being null is not covered. I have older code that deals with the null case, because earlier the spec pushed the head pointer onto the stack in more cases. 

To save the trouble of implementors reasoning about the characteristics of the algorithm, it would be nice to add a note that the after head state cannot be reached in the fragment mode and, thus, the pointer cannot be null.
Comment 1 Henri Sivonen 2009-01-13 18:07:06 UTC
Or more to the point, the after head cannot be reached without going through a mode that sets the head pointer.
Comment 2 Maciej Stachowiak 2010-03-14 13:16:10 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.