On Jan 23, 2006, at 3:54 PM, Eoghan wrote:
I agree that modifying the event object is undesirable, however, I
think there is a strong case to add standard w3c event methods if
missing (IE, Safari < 2) such as event.preventDefault.
so that you could use
...connect(myElement, "onclick", function(e){e.preventDefault()});
without thinking twice about some browsers not implementing the
standard?
MochiKit doesn't modify built-in things, period. If you read one of
Beau's recent messages in this thread, you'll see that a proxy object
is used instead of mangling the event object. This lets us fix
browser bugs, but still provides access to the raw unscathed event
object if you actually want it. Everybody wins, even IE users.
Safari < 2 isn't supported.. so I'm not too worried about that. I'm
sure some of MochiKit works there, but I only test on the latest
version of Mac OS X -- which means Safari 2.0.3 right now.
If someone wants to maintain Safari 1.x support (or any other
currently untested platform)... start by testing and filing bugs
(with patches), and I'll be more than happy to give commit access to
anyone who proves that they are interested and capable in fixing
platform-specific bugs without breaking the other platforms.
-bob
