#226 new
sxeraverx

Effect.multiple should always execute in parallel, regardless of 'queue' setting

Reported by sxeraverx | July 21st, 2009 @ 10:43 AM

Tested on FF3 & FF3.5;

When Effect.multiple is invoked, and put at the end of a queue, the beginning of the effect for multiple elements should be put at the end of the queue together, to start at the same time, and not one after another, as it is now.

Effect.multiple(
  [
    $("elem_1"),
    $("elem_2")
  ],
  Effect.Pulsate,
  {
    speed: 0,
    queue: 'end'
  }
);

The preceding code pulsates the two elements in sequence, instead of in parallel, as it should.

No comments found

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

Pages