> So what?
>
> Rename bind() to on(), unbind() to un()? What about trigger?
> Leave it?

I would vote for all of that, with a compat plugin of course.

> Would you rather screw shortcuts like click() completely? 
> on("click", function) isn't that much longer then click(function)
> anyway. It would help removing any ambiguity: on("unload")
> is pretty clear, un("load") too.

I think it's more confusing to have an exception for .click than to just use
.on("click", fn) but I'm not fanatic about it.

> With the above at hand, do we really need all those shortcuts
> or macros anymore? By using on(), un(), trigger(), css() and
> attr() the API is pretty clean and easy to learn, and the
> different in necessary code to type is minimal. And it's still
> extremely easy to write your own macros if needed.

>From John's last post it sounded like they were already on their way out. It
will be interesting to see how much code that saves. It certainly is going
to simplify the documentation by a factor of two or three.




_______________________________________________
jQuery mailing list
[email protected]
http://jquery.com/discuss/

Reply via email to