Hi, I've included the recommended changes and tested against the nightly, all working fine.
http://gsgd.co.uk/sandbox/jquery.easing.php So, am I ahead of the game in releasing a 1.1.3 ready plugin (admittedly because I didn't do it right in the first place)? Incidently the new plugin page seems to be borked, I can drill down to the Animation and Effects category. Cheers, George. On Jun 25, 12:17 am, "John Resig" <[EMAIL PROTECTED]> wrote: > Yes, it would be preferred - I posted that as the solution to the > ticket discussing the issue, but two issues: > 1) This is a minor release (minor releases shouldn't have any > regressions - and breaking a plugin would be one). > 2) None of theeasingplugins have been updated yet - making it kind > of difficult to ask people to upgrade. > > So, for now, it's a simple change to jQuery core, which has already > been made. I guess we'll have to live with it for now. > > --John > > On 6/24/07, Michael Schuerig <[EMAIL PROTECTED]> wrote: > > > > > On Sunday 24 June 2007, John Resig wrote: > > > Just to clarify: This was an issue in jQuery 1.1.3a - we've fixed the > > > code in jQuery to fall back to 'linear' if it exists (thus causing > > > the code to work, no problem). This fix is in SVN right now and will > > > be in the final 1.1.3 release. > > > I'm wondering, wouldn't it be more appropriate if theeasingplugin > > added to the jQuery.easingnamespace instead of overwriting it? > > Something like > > > jQuery.extend(jQuery.easing, { > > ... > > }); > > > Then,easingfunctions already defined elsewhere would only be replaced > > if there actually was another implementation of them. > > > Michael > > > -- > > Michael Schuerig > > mailto:[EMAIL PROTECTED] > >http://www.schuerig.de/michael/
