- From: Marcos Caceres <marcosscaceres@gmail.com>
- Date: Wed, 28 Jan 2009 19:59:18 +0000
- To: Ian Hickson <ian@hixie.ch>
- Cc: Boris Zbarsky <bzbarsky@mit.edu>, public-webapps <public-webapps@w3.org>
On Wed, Jan 28, 2009 at 7:54 PM, Ian Hickson <ian@hixie.ch> wrote: > On Wed, 28 Jan 2009, Marcos Caceres wrote: >> On 1/23/09 2:25 PM, "Boris Zbarsky" <bzbarsky@MIT.EDU> wrote: >> > >> > "There may be implementation-specific limits on the range of >> > integers allowed, and behavior outside such limits is undefined." >> >> You should probably tell the HTML5 guys about this too, as it may be >> relevant there. > > HTML5 already says: > > User agents may impose implementation-specific limits on otherwise > unconstrained inputs, e.g. to prevent denial of service attacks, to > guard against running out of memory, or to work around > platform-specific limitations. > > ...and there are several other statements in the spec to handle specific > cases (e.g. out-of-JS-Number-range attribute values reflected into the > DOM, or handling out-of-control scripts). Thanks for the clarification. Useful statement, I'll add that somewhere too into the spec. -- Marcos Caceres http://datadriven.com.au
Received on Wednesday, 28 January 2009 19:59:53 UTC