I was just doing some putImageData tests last night, and found that
firefox does not allow putImageData to specify a target that extends
beyond the bounds of the canvas. Given that getImageData can request
bounds that extend beyond the canvas region (3.14.11.1.10) I would
expect to be
Anne van Kesteren wrote:
On Sat, 12 May 2007 17:54:25 +0200, Anne van Kesteren [EMAIL PROTECTED]
wrote:
These features are nice but I don't think authors will understand that
imagedata.height != canvas.height (likewise for width). Authors will
just make something that works in their browser
These features are nice but I don't think authors will understand that
imagedata.height != canvas.height (likewise for width). Authors will just
make something that works in their browser and then assume it will work
everywhere else. Which would horribly break. Even the more experienced
On 12/05/07, Anne van Kesteren [EMAIL PROTECTED] wrote:
These features are nice but I don't think authors will understand that
imagedata.height != canvas.height (likewise for width). Authors will just
make something that works in their browser and then assume it will work
everywhere else. Which
On 12/05/07, Philip Taylor [EMAIL PROTECTED] wrote:
On 12/05/07, Anne van Kesteren [EMAIL PROTECTED] wrote:
These features are nice but I don't think authors will understand that
imagedata.height != canvas.height (likewise for width). Authors will just
make something that works in their
On Sat, 12 May 2007 17:54:25 +0200, Anne van Kesteren [EMAIL PROTECTED]
wrote:
These features are nice but I don't think authors will understand that
imagedata.height != canvas.height (likewise for width). Authors will
just make something that works in their browser and then assume it will
On 12/05/07, Anne van Kesteren [EMAIL PROTECTED] wrote:
The best way forward would probably be to get rid of canvas device
pixels and just make such a pixel map a canvas pixel. This means that
getImageData() and putImageData() work similarly to toDataURL() and
drawImage(). If people really want
