We (the dev team) talked it over and since we released the fix (and replaced 1.1.2 so quickly) we opted to leave it as 1.1.2 instead of bumping it up to 1.1.3. We had the fix in place within hours of the original blog post.
It's a tricky line to balance. We either get to replace 1.1.2 and cause some possible confusion with Safari issues (for users who upgraded very quickly) or push out 1.1.3 and cause more confusion having two releases occur in just a couple hours. That's the reasoning behind why we didn't push a 1.1.3 release out the door immediately, that being said, it's still possible that we could get a 1.1.3 release out quickly (maybe sometime this week) - which would, of course, include this fix. --John On 3/5/07, Seb Duggan <[EMAIL PROTECTED]> wrote: > Is there any way you could re-release this as 1.1.3? > > The people who use jQuery are very likely to update their websites > with any new point release, but maybe not with a re-release of the > same version. > > I've already come across a number of sites (mostly demos of plugins) > that crash Safari because they're using the initial 1.1.2 release. > And for most of them, it won't be an issue they'll know about because > they're not using Safari... > > > Seb > > > On 5 Mar 2007, at 18:01, Seb Duggan wrote: > > > Yes, fixes my problem too... > > > > > > Seb > > > > _______________________________________________ > jQuery mailing list > discuss@jquery.com > http://jquery.com/discuss/ > _______________________________________________ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
