11749 2011-01-13 19:55:45 +0000 Do we really want values to wrap instead of clamping? 2011-05-24 22:26:15 +0000 1 1 1 Unclassified WebAppsWG WebIDL unspecified All All RESOLVED WONTFIX P2 normal --- 1 ayg cam bzbarsky mike Ms2ger public-script-coord public-webapps-bugzilla oldest_to_newest 44331 0 ayg 2011-01-13 19:55:45 +0000 The algorithm to convert ECMAScript values to various IDL types (octet, short, etc.) specifies that they wrap if they're out of range, by saying that they're taken mod 2^8 or 2^16 or whatever. Is this behavior really necessary? Clamping to the nearest allowed value is much nicer behavior, if it's compatible with how browsers behave. 44333 1 bzbarsky 2011-01-13 20:57:13 +0000 Is it compatible? (Note that generally wrapping is faster to do, so unless there's a good reason to expect that people will need to rely on the clamping it's easier to not support it.) 48754 2 cam 2011-05-24 22:26:15 +0000 I don't know about compatibility with content. I'm inclined to leave it as is, for the reason Boris states, and that the wrapping is what the ES5 spec uses when builtin functions need to convert a value to an integer. FWIW, data:text/html,<script>a=document.createElement("input");a.size=4294967297;alert(a.size)</script> alerts "1" (4294967297 being 2^32+1) in Firefox, Safari, Chrome and IE. In Opera it alerts "-2147483648"