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

[Bug 14505] Rules for signed/non-negative integers doesn't handle overflow

From: <bugzilla@jessica.w3.org>
Date: Wed, 19 Oct 2011 09:26:14 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1RGSPe-0004c4-S2@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14505

--- Comment #1 from Mounir Lamouri <mounir.lamouri@gmail.com> 2011-10-19 09:26:13 UTC ---
It seems that reflection takes into account overflow [1] but it should probably
be moved somewhere else or the check of "in attribute type range" should be
copy-pasted at a lot of places.

For example, if maxlength content attribute is a too high number, higher than
long range, maxlength IDL attribute will return -1. However, the input element
will be considered as having a maxlength and the maxlength value should be used
to check if the element's value is too long [2].

I'm not sure what would be the best way to handle that..

[1]
http://www.whatwg.org/specs/web-apps/current-work/multipage/common-dom-interfaces.html#reflecting-content-attributes-in-idl-attributes
[2]
www.whatwg.org/specs/web-apps/current-work/multipage/association-ofcontrols-and-forms.html#maximum-allowed-value-length

-- 
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 Wednesday, 19 October 2011 09:26:23 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:02:06 UTC