[Bug 12296] New: 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

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

           Summary: 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
           Product: HTML WG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-work/#sig
                    ned-integers
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: contributor@whatwg.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


Specification:
http://www.whatwg.org/specs/web-apps/current-work/multipage/common-microsyntaxes.html
Section: http://www.whatwg.org/specs/web-apps/current-work/#signed-integers

Comment:
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="&nbsp;2"><script>alert(document.querySelector("input").tabIndex);</s
cript>

Posted from: 68.175.61.233
User agent: Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/534.20 (KHTML,
like Gecko) Chrome/11.0.672.2 Safari/534.20

-- 
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:30:50 UTC