I currently do this:
Event.DOMEvents.push((Prototype.Browser.Gecko) ? 'DOMMouseScroll' :
'mousewheel');
when I define my custom signalConnect functions, so that the
mousewheel event will work. Thought I'd like for this and the enter/
leave events to be integrated, so that I can remove this
On 8/20/07, kangax [EMAIL PROTECTED] wrote:
I did something similar for my context menu script.
Since 1.6.0_rc0 does not have 'contextmenu' event and latest build in
a trunk does, I worked around it like so:
Simply use trunk until the 1.6.0 final release.
On 8/20/07, kangax [EMAIL PROTECTED] wrote:
Of course, but if it's a public extension
Oh, didn't realize this. Well, yeah, you can do these tiny conditional
hacks. I hope we release the final soon
--~--~-~--~~~---~--~~
You received this message because you are
On 8/17/07, Viktor Kojouharov [EMAIL PROTECTED] wrote:
However, there's still the issue of having
support for global element events, like 'mousewheel', 'mouseenter',
and 'mouseout', that would work with all elements, and reuse existing
event names to achieve their function.
In the old
On Aug 17, 1:24 pm, Mislav Marohnić [EMAIL PROTECTED]
wrote:
On 8/17/07, Viktor Kojouharov [EMAIL PROTECTED] wrote:
However, there's still the issue of having
support for global element events, like 'mousewheel', 'mouseenter',
and 'mouseout', that would work with all elements, and
