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

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

From: Jim Ley <jim@jibbering.com>
Date: Fri, 6 Jan 2006 09:40:50 -0000
To: www-svg@w3.org
Message-ID: <dpldv7$1r5$1@sea.gmane.org>


"Boris Zbarsky" <bzbarsky@mit.edu> wrote in message 
news:43BD9053.8040806@mit.edu...
> Jim Ley wrote:
>> "Maciej Stachowiak" <mjs@apple.com> wrote in message 
>> news:342DB765-C2C1-4F74-BCB3-423572ED3DE5@apple.com...
>>> * Removing a <handler> element doesn't remove the corresponding event 
>>> handler on its observer.
>>> * Inserting a <handler> element doesn't add an event handler on its 
>>> observer unless this happens as part of parsing.
>>> * Changing the text contents of even an inline handler element  doesn't 
>>> change what happens when the event fires.
>>>
>>> All of these seem counter-intuitive, contrary to how the <listener> 
>>> element works, and contrary to how "onfoo" style inline event 
>>> attributes work.
>>
>> Er, this is exactly equivalent to how on ofoo inline events work I would 
>> say.
>
> Jim, I'm not sure I follow.  Changing the onclick attribute of an HTML 
> node certainly affects what happens when the click event fires.

el.setAttribute("onclick","alert(1)");

Does not mean the alert is produced it does in some implementations, it does 
not in others, the specification is silent on the matter.

Jim. 
Received on Friday, 6 January 2006 09:41:24 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:33 GMT