[Bug 12296] Rules for parsing an integer don't match ES parseInt()

http://www.w3.org/Bugs/Public/show_bug.cgi?id=12296

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |WONTFIX

--- Comment #9 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-08-03 00:32:56 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 main way in which the HTML spec's algorithm is superior to the
ES algorithm is that ES' algorithm changes every time Unicode add new
whitespace characters. It's also simpler to implement (either from scratch —
it really is a simpler algorithm — or, if you're going to use a library, it's
simpler because you would only need to use an HTML library which you're likely
already and which is likely to expose this as a function explicitly using
rather than having to find a JS library that exposes this particular
algorithm), and simpler to understand from an authoring perspective. It's also
easier to spec (no need to track another spec with moving references, not to
mention that that spec itself tracks another one), and easier to understand
when reading the spec.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Wednesday, 3 August 2011 00:32:58 UTC