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 11428 - The steps for "A sequence of bytes starting with a 0x3C byte (ASCII <), optionally a 0x2F byte (ASCII /), and finally a byte in the range 0x41-0x5A or 0x61-0x7A (an ASCII letter)" seems bogus if the read byte in step 1 is ">". Consider <html>a="<meta char
Summary: The steps for "A sequence of bytes starting with a 0x3C byte (ASCII <), optio...
Status: RESOLVED WORKSFORME
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-29 15:00 UTC by contributor
Modified: 2011-08-04 05:17 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2010-11-29 15:00:21 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/complete/parsing.html
Section: http://www.whatwg.org/specs/web-apps/current-work/#documentEncoding

Comment:
The steps for "A sequence of bytes starting with a 0x3C byte (ASCII <),
optionally a 0x2F byte (ASCII /), and finally a byte in the range 0x41-0x5A or
0x61-0x7A (an ASCII letter)" seems bogus if the read byte in step 1 is ">".
Consider <html>a="<meta charset=utf-8>"

Posted from: 85.227.152.46
Comment 1 Jenn Braithwaite 2010-11-30 19:47:39 UTC 
The steps make sense.  The instructions under "get an attribute" handle the case if the read byte is '>'.
Comment 2 Simon Pieters 2010-12-01 09:43:08 UTC 
Indeed.
Comment 3 Michael[tm] Smith 2011-08-04 05:17:29 UTC 
mass-move component to LC1