W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > May 2011

[Bug 12220] Make sure rules for parsing a float are the same in HTML and in Javascript specifications

From: <bugzilla@jessica.w3.org>
Date: Thu, 05 May 2011 21:16:01 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QI5tx-0008QZ-3m@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12220

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |ian@hixie.ch
         Resolution|                            |FIXED

--- Comment #7 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-05-05 21:16:00 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: Accepted
Change Description: see diff given below
Rationale:

We can't use the exact parseFloat() algorithm since that supports things like
"Infinity".

I've fixed the algorithm to support the syntax ES supports, though. These
mistakes were unintentional.

-- 
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 Thursday, 5 May 2011 21:16:02 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:09 UTC