#41 new

Effect.Shake afterFinish not supported

Reported by pgib | July 8th, 2008 @ 08:26 PM | in 1.8.3 bugfix release

The afterFinish callback does not seem to get called when using Effect.Shake.

For a live example, see:


(source attached)

Comments and changes to this ticket

  • pgib

    pgib July 8th, 2008 @ 08:27 PM

    (Using script.aculo.us 1.8.1 and Prototype

  • Vlad

    Vlad September 18th, 2008 @ 12:06 AM

    • Tag changed from afterfinish, effect.shake, scriptaculous to afterfinish, effect.shake, scriptaculous

    Looks like the last Effect.Move in that effect does not try to inherit any events that are passed along in the options. This has worked for me - changing the last call to Effect.Move to:

    new Effect.Move(effect.element,

      Object.extend({ x: -distance, y: 0, duration: split, afterFinishInternal: function(effect) {
      }}, options)) }}) }}) }}) }}) }});
  • ronin-15560 (at lighthouseapp)

    ronin-15560 (at lighthouseapp) November 20th, 2008 @ 08:51 PM

    • Milestone set to 1.8.3 bugfix release
  • petrm

    petrm March 26th, 2010 @ 09:22 AM

    I am sorry to confirm that in 1.8.3 is this bug too

  • petrm

    petrm December 26th, 2010 @ 01:15 PM

    • Importance changed from “” to “”

    Same in 1.9.0

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

script.aculo.us is an open-source JavaScript framework for visual effects and interface behaviours.
<br/><b>Source available from github</b>
The Git repository resides at:
<a href="http://github.com/madrobby/scriptaculous">http://github.com/madrobby/scriptaculous</a>
<br/>Check out the current development trunk with:
<code>git clone git://github.com/madrobby/scriptaculous.git</code>
<br/>As <b>script.aculo.us 1.xx is feature-frozen</b>, this development trunk is for <b>bugfixes only</b>.
<br/>New development should happen only for
<b>script.aculo.us 2</b>.
<br/><b>Creating a bug report</b>
When creating a bug report, be sure to include as much relevant information as possible. Post a an example that shows off the problem. Preferably, <b>alter the unit tests</b> and show through either changed or added tests how the expected behavior is not occuring.

People watching this ticket