The new custom event code in the trunk branch checks whether the name of an event to be observed is in Event.DOMEvents and if not assumes that the name is meant to be a custom event and piggyback it on top of an ondtatavaiable event. Event.DOMEvents only contains event names that are available on all supported browsers. The problem with this is that it breaks existing code such as the following excerpt: this.mw_fx=this.MouseWheel.bindAsEventListener(this); Event.observe(document,''mousewheel'',this.mw_fx,false); Event.observe(document,''DOMMouseScroll'',this.mw_fx,false); This gets broken because mousewheel and DOMMouseScroll (which are not included in Event.DOMEvents) are now assumed to be the names of custom events, and therefore the actual events from the browser are no longer captured. What is the recomended prototype way of dealing with this now that Event.observe can no longer be used to watch an event that is not generated by all browsers ?? (I would rather not go back to checking for the existence of addEventListener or attachEvent and using whichever exists, since that was nicely cleaned up by the prior implementation of Event.observe) Tom --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---