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 22027 - For <pre>, <listing>, and <textarea>, the "next token" is not well-defined. For example, does a NULL character token count, if it is ignored by tree construction?
Summary: For <pre>, <listing>, and <textarea>, the "next token" is not well-defined. F...
Status: RESOLVED DUPLICATE of bug 22026
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-14 04:25 UTC by contributor
Modified: 2013-05-14 04:28 UTC (History)
2 users (show)

See Also:

Attachments

Description contributor 2013-05-14 04:25:47 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/tree-construction.html
Multipage: http://www.whatwg.org/C#the-after-head-insertion-mode
Complete: http://www.whatwg.org/c#the-after-head-insertion-mode
Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/

Comment:
For <pre>, <listing>, and <textarea>, the "next token" is not well-defined.
For example, does a NULL character token count, if it is ignored by tree
construction?

Posted from: 110.142.158.46
User agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0
Comment 1 Michael Day 2013-05-14 04:28:39 UTC 

*** This bug has been marked as a duplicate of bug 22026 ***