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

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

From: <bugzilla@jessica.w3.org>
Date: Mon, 14 Mar 2011 14:16:34 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Pz8ZW-0003Fb-N9@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12296

Aryeh Gregor <Simetrical+w3cbug@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Whitespace handling here    |Rules for parsing an
                   |doesn't match ES, or Gecko, |integer don't match ES
                   |or Opera.  Is there some    |parseInt()
                   |reason to not just say it   |
                   |works the same as parseInt? |
                   | Test case alerts 2 in      |
                   |Firefox and Opera (like     |
                   |parseInt()), 0 in Chrome:   |
                   |data:text/html              |
            Summary|<!doctype html><input       |
                   |tabindex="&nb               |

-- 
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 Monday, 14 March 2011 14:16:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 14 March 2011 14:25:17 GMT