On Tue, Nov 30, 2010 at 3:11 AM, Johan Arensman <johanm...@gmail.com> wrote: > http://api.prototypejs.org/dom/Event/observe/ > > Changes in 1.6.x > > Prior to Prototype 1.6, Event.observe supported a fourth argument > (useCapture), a boolean that indicated whether to use the browser's > capturing phase or its bubbling phase. Since MSIE does not support the > capturing phase, we removed this argument from 1.6, lest it give users the > false impression that they can use the capturing phase in all browsers. > > 1.6 also introduced setting the this context to the element being observed, > automatically extending the Event object, and the Event#findElement method.
It doesn't make sense to omit an important part of event handling, in all browsers, in order to prevent Javascript beginners who don't know the basics of event handling support from being confused for a couple minutes. It's very inconvenient to have to handle these events manually. Instead of being able to keep an array of Handlers that I can uniformly stop, I have to revert to manual addEventListener/removeEventListener calls for a couple. All it needs is a Prototype.BrowserFeatures.EventCapture, and maybe throw an exception if capturing is used when it's not supported (even that seems overkill). -- Glenn Maynard -- You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" group. To post to this group, send email to prototype-scriptacul...@googlegroups.com. To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en.
