#200 new

BlindDown() and BlindUp() fails in functional_tests

Reported by Marcus | May 2nd, 2009 @ 03:01 PM


Environment : script.aculo.us version 1.8.2; Prototype version; Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv: Gecko/2008092417 Firefox/3.0.3;

same with: Internet Explorer 8.0.6001.18372; Opera 9.21 Build 8776; Safari(Win) 3.1.2 (525.21)

All Unit tests succeded. No failures, no errors!

Problem : Using BlindDown() and BlindUp() works fine using it slowly! But when clicking on BlindUp() and when its folded clicking on BlindUp() again and rapidly BlindDown(), nothing but a short wobble appears. Clicking again on BlindDown() makes the text-box appear again, but the Links for BlindDown() and BlindUp() stay at top over the text-box.

Comments and changes to this ticket

  • neilgrimes

    neilgrimes August 27th, 2009 @ 05:03 PM

    I have also noticed an issue that I think is the same as this.

    Basically a double click of the blinddown link causes the blinddown to happen over the top of the rest of the text - sort of overlapping.

    See attached.

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