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 7079 - Inconsistency in algorithm descriptions for parsing integers
Summary: Inconsistency in algorithm descriptions for parsing integers
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P5 trivial
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Depends on:
Reported: 2009-07-05 18:14 UTC by Lachlan Hunt
Modified: 2010-10-04 14:49 UTC (History)
3 users (show)

See Also:


Description Lachlan Hunt 2009-07-05 18:14:30 UTC
In the rules for parsing non-negative integers and the rules for parsing integers, there is some inconsistency in the way the two algorithms are written.

Step 9.4 in the first is written as:
"If position is not past the end of input, return to the top of the step labeled
 loop in the overall algorithm..."

In the latter algorithm, it's written as:
"If position is not past the end of input, return to the top of step 9 in the
 overall algorithm"

Please write these two algorithms using consistent language.
Comment 1 Ian 'Hixie' Hickson 2009-08-08 01:45:08 UTC
I would rather not make editorial changes to the algorithms since that is what leads to mistakes.
Comment 2 Maciej Stachowiak 2010-03-14 14:48:23 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.