- From: Boris Zbarsky <bzbarsky@mit.edu>
- Date: Fri, 06 Jan 2006 08:04:09 -0600
- To: Jim Ley <jim@jibbering.com>
- CC: www-svg@w3.org
Jim Ley wrote:
> > >> 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.
Yes, but in all browser implementations with significant market share (so I'm
excluding things like lynx here), it's implemented interoperably and produces an
alert when the "click" event fires. I fully expect this to be formally
standardized by either W3C or WHATWG in the near future.
We all realize most of DOM0 is not specified yet, but Maciej's point as I
understood it was that <handler> _is_ being specified, and is being specified in
a way that doesn't match either the de-facto DOM0 behavior or the behavior of
<listener>.
So I still fail to see what's "exactly equivalent" about the two situations.
Received on Friday, 6 January 2006 14:04:30 UTC