Not to sound rude or anything, but I'd really like to alter Prototypes Event methods to fix the problem. I don't want to have to make special cases for everything I do or create/include a bunch of different classes/objects to get things to work. And order is important in my case because I use PHP classes that output their own Event.observe registrations, and the registrations I make in the scripts using those PHP classes depend on objects created by the former registrations. That probably didn't make sense, but, nonetheless, order is important. In any case, I thought the point of Prototype was to create a library of cross-browser compatible utilities, and technically Event.observe does not produce the same results across browsers.
I'd to note that the code that I posted had many flaws which I attempted to fix (ie. calling observers every time elements matched and detaching the observeIE method on a stopObserving call), but it still was producing odd behavior. In any case, if anybody has any other suggestions as to how I can alter the Event methods to make IE call the observers in order, I'd greatly appreciate it. Thanks, Matt --~--~---------~--~----~------------~-------~--~----~ 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 [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
