W3C home > Mailing lists > Public > whatwg@whatwg.org > December 2009

[whatwg] Canvas.cloneNode()

From: Ian Hickson <ian@hixie.ch>
Date: Wed, 9 Dec 2009 17:08:29 +0000 (UTC)
Message-ID: <Pine.LNX.4.62.0912091707060.29336@hixie.dreamhostps.com>
On Fri, 30 Oct 2009, OmegaJunior wrote:
> 
> Since Last Call was announced and I just ran into this problem, hereby 
> this question:
> 
> If an image is drawn on a Canvas element, and subsequently the 
> javascript function cloneNode(true) is executed for that element, should 
> the clone include a copy of the source canvas image, or should it show 
> an empty space?
> 
> From my perspective (the web author), I'd prefer to have the canvas 
> image included when executing (the deep) cloneNode(true), and excluded 
> it when using (the shallow) cloneNode(false).

The cloneNode() method just clones the node, not the node's state, so the 
bitmap isn't copied. You can easily draw one bitmap onto the other, 
though, using drawImage().


On Sat, 14 Nov 2009, Michael A. Puls II wrote:
> 
> I think it'd be cool if the clone showed the image. But, I'm pretty sure 
> cloneNode(true) is just supposed to create a new canvas element with the 
> same attributes and childNodes as the original. It's not supposed to 
> copy everything that's going on with the element being copied.
> 
> There are some exceptions with state for certain elements. Perhaps that 
> can happen with canvas too.

I'd rather keep these exceptions to an absolute minimum. cloneNode() is 
part of the DOM Core API, and it would be bad for nodes to clone 
differently based on whether it's an HTML-aware UA implementing the DOM 
Core API or not.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Wednesday, 9 December 2009 09:08:29 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:54 UTC