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 5798 - Deferring end tag eating to after head gives weird errors
Summary: Deferring end tag eating to after head gives weird errors
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-06-24 20:01 UTC by Henri Sivonen
Modified: 2010-10-04 13:58 UTC (History)
3 users (show)

See Also:


Description Henri Sivonen 2008-06-24 20:01:56 UTC
'After head' is now defined to eat all end tags. If the state is 'in head' and there's a stray end tag, subsequently things happen in the 'after head' state which means that stuff that does belong in <head> is in error but ends up in <head> anyway. Intuitively, the stray end tag is in error, but normal <head> children after it aren't.

It might be worthwhile to adjust things so that the stuff that usually belongs in <head> doesn't emit errors if there was an ignored end tag first.
Comment 1 Ian 'Hixie' Hickson 2008-06-25 21:16:37 UTC
Comment 2 Ian 'Hixie' Hickson 2008-06-30 23:42:03 UTC
Wait, what? A stray end tag in "in head" is ignored as well. Can you give an example of what you mean?
Comment 3 Maciej Stachowiak 2010-03-14 13:14:28 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.