- From: <bugzilla@jessica.w3.org>
- Date: Tue, 18 Oct 2011 23:06:01 +0000
- To: public-html@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14505 Summary: Rules for signed/non-negative integers doesn't handle overflow Product: HTML WG Version: unspecified Platform: PC OS/Version: All Status: NEW Severity: normal Priority: P2 Component: HTML5 spec (editor: Ian Hickson) AssignedTo: ian@hixie.ch ReportedBy: dbates@webkit.org QAContact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-wg-issue-tracking@w3.org, public-html@w3.org This issue was brought up in the WHATWG email thread <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-October/033508.html>. The sections on parsing signed/non-negative integers doesn't describe what should happen when the sequence of collected characters interpreted as a base ten-integer isn't representable using an integer datatype. In particular, step 8 in both of these sections doesn't mention how to handle this case. Because the rules for parsing a signed/non-negative integer don't return an error for such a case, it's up to the UA to handle it as it sees best despite the fact that many portions of the spec have defined behavior for handling an error that is returned when parsing an integer (e.g. "Sequential focus navigation and the tabindex attribute"). That is, the spec isn't always falling back on its error handling definitions when it could. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Received on Tuesday, 18 October 2011 23:06:03 UTC