Someone sent me an email the other day, asking that I add shorthand methods for
.unbind(eventType) to the jQuery core file. He argued that since jQuery provides shorthands such as
.bind('click'), it should also include
.unbind('click') for consistency. But he didn’t consider two things:
- I can’t change jQuery’s API.
- Those shorthand methods used to be part of jQuery core, but with the release of 1.0, John Resig cleaned up the API quite a bit, removing all of the
While I understand the desire for simplicity in developers’ code and consistency in jQuery’s API, I think Mr. Resig made the right decision removing the shorthand methods. Keeping both “un” and “one” shorthands in there would have meant an additional 44 methods, with very little gain for most users of the library. Nevertheless, it’s fairly trivial to create a plugin for this sort of thing.
A long time ago I built myself a little bookmarklet to load jQuery on pages that don’t already have it. The idea was to allow me to play around with any page on the web, using jQuery in the Firebug (and now Safari or IE8) console. I blogged about it, got lots of great feedback, and then blogged about an improved version. Now that a lot more great feedback has come through the comments of the updated bookmarklet post, I’ve decided to update it one more time.
Since the release of jQuery 1.3 a month and a half ago, I’ve been keeping my eye on any troubles that people have had with their upgrades. Fortunately, most people have had no problems at all. For those who have, the issues have almost always been in one of three areas. Identifying these areas and adjusting any legacy scripts ahead of time will go a long way toward ensuring a smooth transition to jQuery 1.3.x.