Diego, on IE custom events can't be cancelled. fireEvent will always
fire an event that bubbles.
http://msdn.microsoft.com/en-us/library/ms536423(VS.85).aspx
That's why I'm for making Element#observe handle mouseenter/leave in
the core. Firing and then filtering custom events goes against the
po
Hello Ryan,
Thanks for the example.
I used this favlet to run the site using the git version of Prototype
and I do see the issue under IE.
javascript:var
s=document.createElement('script');s.setAttribute('src', 'http://
www.protolific.net/prototype-git.js');document.body.appendChild(s);void(s);
Nick,
my suggestion was to use standard native events in
user code, not custom events in the core:
mouseover (bubbles and is cancelable).
The user should then take care of cancelling the event
himself if he does not use the bubbling phase or if
is disturbing to have ancestors be notified.
--
Di
On Jun 12, 5:46 am, Nick Stakenburg <[EMAIL PROTECTED]> wrote:
> I've been saying this for some time but custom events seem to be used
> as an excuse not to implement this properly, like other frameworks
> have done. Of course it can be done with custom events but it's
> clearly not the best appro
[1] http://msdn.microsoft.com/en-us/library/ms536956(VS.85).aspx
[2] http://msdn.microsoft.com/en-us/library/ms536910(VS.85).aspx
(Just pretend I included these in the original message.)
On Jun 12, 8:20 pm, Andrew Dupont <[EMAIL PROTECTED]> wrote:
> On Jun 12, 5:46 am, Nick Stakenburg <[EMAIL PR
