> Don't remove the shortcuts, please! They are very convenient
> for the events. I can understand that css() and attr() can be
> enough. But click() as it is now is Easy and Clear and Convenient.
> The unbind could be incorporated into click() too, for example
> by using click( null );
Event shortcuts are the major namespace polluter. Each one requires an
implementation, which is usually rather simple, but also documentation. What
about the ability to pass data from the bind or trigger handlers, how would
that be done? If it's not added to these interfaces, then you'll end up with
a mix of .click() and .on("click", fn, {data: whatever}) in the page. If it
is added, then there are a couple of dozen event-methods that require
additional explanation for how they behave.
You can't unbind a single click handler with the .click(null) approach; you
can only unbind all click handlers for the element. That becomes very
important when a page uses multiple plugins that may need event handlers. In
a plugin, you can't assume that just because you want to clear your own
handler that it's okay to clear all of them. It's even a dangerous
assumption to make when developing a page, unless you are familiar with the
internals of all the plugins you are using.
Then there is the classic ambiguity of .unload(). Does it call an onunload
handler, or does it unbind all onload handlers? There is no doubt with
.un("load") or .on("unload", fn) which are only a few characters longer.
Don't worry, nobody is proposing changes that require a fire drill to fix.
There will be a plugin to provide all the 1.1 names and I suspect the
default build will include it for at least a few months to make the
transition easier.
_______________________________________________
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
