#264 new
Jan Nejman

DropOut effect - invalid positioning

Reported by Jan Nejman | December 15th, 2009 @ 02:22 PM

After running a "DropOut" effect the block is moved 100px below. If you run .appear and dropout again,
the text goes down and down.

If sugest the follwoing patch:

effects.js:

line 640:
return new Effect.Parallel( [ new Effect.Move(element, {x: 0, y: 100, sync: true }), new Effect.Opacity(element, { sync: true, to: 0.0 }) , new Effect.Move(element, {x: 0, y: 0, sync: true }) ], // new - move back to the original position

...

Or did I miss something?

Jan

Comments and changes to this ticket

  • Jan Nejman

    Jan Nejman December 15th, 2009 @ 02:40 PM

    Sorry, the patch doesn't help. I don't know how to recover the position after effect... ;-(
    afterFinishInternal: function(effect) {
    effect.effects[0].element.hide().undoPositioned().setStyle(oldStyle);

    doesn't work.

    Jan

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