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

[Bug 12296] Whitespace handling here doesn't match ES, or Gecko, or Opera. Is there some 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,<!doctype html><input tabindex="&nb

From: <bugzilla@jessica.w3.org>
Date: Sun, 13 Mar 2011 22:32:30 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Pytpu-0001VX-Dm@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12296

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |Simetrical+w3cbug@gmail.com

--- Comment #1 from Aryeh Gregor <Simetrical+w3cbug@gmail.com> 2011-03-13 22:32:30 UTC ---
More copy-pasteably:

data:text/html,<!doctype html>
<input tabindex="&nbsp;2">
<script>
alert(document.querySelector("input").tabIndex);
</script>

ES spec:

http://es5.github.com/#x15.1.2.2

I didn't spot any difference other than whitespace handling, but it would be
simpler for everyone if we reused the same definition and said this worked like
parseInt(x, 10).

-- 
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 Sunday, 13 March 2011 22:32:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 13 March 2011 22:32:32 GMT