5798 2008-06-24 20:01:56 +0000 Deferring end tag eating to after head gives weird errors 2010-10-04 13:58:22 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified All All VERIFIED INVALID NoReply P2 normal --- 1 hsivonen ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 20815 0 hsivonen 2008-06-24 20:01:56 +0000 '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. 20872 1 ian 2008-06-25 21:16:37 +0000 Yeah. 21000 2 ian 2008-06-30 23:42:03 +0000 Wait, what? A stray end tag in "in head" is ignored as well. Can you give an example of what you mean? 32959 3 mjs 2010-03-14 13:14:28 +0000 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: http://dev.w3.org/html5/decision-policy/decision-policy.html 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.