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 8143 - [gsnedders] Need to add EOF here, as <xmp>foo</xmp behaviour changed when removing content model flags (also to similar RCDATA state).
Summary: [gsnedders] Need to add EOF here, as <xmp>foo</xmp behaviour changed when rem...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 critical
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords: NE
Depends on:
Blocks:
 
Reported: 2009-11-01 12:11 UTC by contributor
Modified: 2010-10-04 14:46 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2009-11-01 12:11:57 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#rawtext-end-tag-name-state

Comment:
[gsnedders] Need to add EOF here, as <xmp>foo</xmp behaviour changed when removing content model flags (also to similar RCDATA state).

Posted from: 83.252.233.86
Comment 1 Geoffrey Sneddon 2009-11-03 17:59:52 UTC 
<gsnedders> Basically, you read rawtext/rcdata end tag name state, and eventually you have in temporary buffer "xmp", and then you hit EOF. When you hit EOF, we should have a case in that state in the parser which just reprocesses the EOF character in the data state
<gsnedders> I guess we should change script data too [for consistency]
Comment 2 Ian 'Hixie' Hickson 2009-11-03 19:49:10 UTC 
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, 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

Status: Rejected
Change Description: no spec change
Rationale: The new behaviour makes more sense, no?

Let me know if you find what the original reason for this behaviour was. I wasn't able to find why we changed this in my very brief search.