W3C home > Mailing lists > Public > www-svg@w3.org > April 2006

Re: SVGT 1.2: dynamic changes to <handler> elements

From: Maciej Stachowiak <mjs@apple.com>
Date: Sat, 1 Apr 2006 01:18:14 -0800
Message-Id: <844D6CFF-D033-485C-BEE3-2E8B64B2A495@apple.com>
Cc: www-svg@w3c.org
To: Jon Ferraiolo <jonf@adobe.com>

On Mar 1, 2006, at 9:23 AM, Jon Ferraiolo wrote:

> Hi Maciej,
> This is the official response to your email
> (http://lists.w3.org/Archives/Public/www-svg/2005Dec/0243.html).
> We absolutely agree with your suggestion. There was a copy/paste error
> when text about the script element was copied into the description of
> the handler element. Thanks for catching this. The old text was:
> ------------------
> Removing, inserting or altering handler elements after their  
> content has
> been loaded has no effect on executable content, but changes made  
> to the
> parameters that are available from a given handler element must be
> reflected when the handler content is executed.
> ------------------
> The new text reads as follows:
> ------------------
> Changes to a handler element's attributes and child nodes must be
> reflected thereafter in event dispatching and when the handler's  
> script
> logic is executed.
> ------------------
> Thanks for your feedback. Please respond within two weeks if this
> response is not satisfactory.

Hi Jon,

Sorry for the late reply, but I somehow missed this message earlier.  
The new text is improved but does not specify what happens when  
removing or inserting handler elements. Also, it's not very clear on  
what "is reflected" means. Does this change the existing event  
listener? Does it unregister the previous one and register a new one?  
Something else mysterious? It would be best to make this explicit in  
terms of concepts from DOM Events. (I think unregister old and  
register new is the best model for reflecting content changes.)

Received on Monday, 3 April 2006 08:06:57 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:47:07 UTC