vladimir at pobox.com
Mon Jun 2 12:03:02 PDT 2008
Sorry it took me a bit to respond here... so, ok, based on the
discussion, I'd suggest:
- user-created ImageData-like objects should be supported, e.g. with
language such as:
The first argument to the method must be an ImageData object returned
by createImageData(), getImageData(), or an object constructed with
the necessary properties by the user. If the object was constructed
by the user, its width and height dimensions are specified in device
pixels (which may not map directly to CSS pixels). If null or any
other object is given that does not present the ImageData interface,
then the putImageData() method must raise a TYPE_MISMATCH_ERR exception.
- ImageData objects returned by createImageData or getImageData should
behave as currently specified; that is, they should explicitly clamp
on pixel assignment.
That gives users a choice over which approach they want to take, and
whether they want clamping or not.
How's that sound?
More information about the whatwg