[whatwg] createImageData -> new ImageData() ?
ian at hixie.ch
Sun Feb 10 15:25:51 PST 2008
On Sun, 10 Feb 2008, Anne van Kesteren wrote:
> On Sun, 10 Feb 2008 10:21:34 +0100, Ian Hickson <ian at hixie.ch> wrote:
> > On Sun, 3 Feb 2008, Anne van Kesteren wrote:
> > > Why not give the object a constructor? I think that's cleaner. Also,
> > > Opera already supports that :-)
> > The relationship between the height and width arguments and the height and
> > width of the ImageData structure returned can vary on a per-canvas basis.
> That would mean that passing ImageData around between two <canvas>
> elements doesn't always work as expected. I think that's highly
> undesirable. Is there any implementation where we know this will the
Not today, but why preclude it? Implementations could get higher quality
renderings on canvases that get resized dynamically, by using a bigger
backing store. What's wrong with what we have now?
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
More information about the whatwg