W3C home > Mailing lists > Public > www-dom@w3.org > July to September 2002

Re: event listeners and ids with Range cloning methods

From: Philippe Le Hegaret <plh@w3.org>
Date: 18 Sep 2002 11:34:54 -0400
To: Dylan Schiemann <dylans@yahoo.com>
Cc: WWW DOM <www-dom@w3.org>
Message-Id: <1032363294.2884.165.camel@jfouffa>

On Mon, 2002-07-15 at 03:11, Dylan Schiemann wrote:
> A couple of questions about the Range for which I'd
> appreciate confirmation or clarification:
> 
> - should cloneContents clone eventListeners?  Based on
> behavior for cloneNode and the Events spec., I would
> guess no.  If it did, this raises issues for
> partially-selected nodes.
> 

We added the following in the Events draft:
	      Copying a Node does not copy the event listeners attached
	      to it. Event listeners must be attached to the newly
	      created node afterwards if so desired. Therefore, when
	      Nodes are copied using Node.cloneNode or
	      Range.cloneContents, the EventListeners attached to them
	      are not automatically attached to their copies.


> - should extractNodes maintain eventListeners? If this
> method is considered cloning, then I would guess no. 
> If so, then I see issues with extracting
> partially-selected nodes.

We added the following in the Events draft:
	      Moving a Node does not affect the event listeners attached
	      to it.  Therefore, when Nodes are moved using
	      Document.adoptNode, Node.appendChild, or
	      Range.extractContents, the EventListeners attached to the
	      moved Nodes stay attached to them.

This should address those issues.

Philippe
Received on Wednesday, 18 September 2002 11:34:57 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:13:56 GMT