Skip to main content

Bug Tracker

Side navigation

#38 closed bug (fixed)

Opened July 04, 2006 09:35PM UTC

Closed July 17, 2006 03:49AM UTC

Last modified March 15, 2012 05:11PM UTC

slideDown from display: none

Reported by: john Owned by:
Priority: critical Milestone: 1.0
Component: effects Version: 1.0
Keywords: Cc:
Blocked by: Blocking:

When revelaing a fieldset that starts out as display: none, it gives an instanteous flickr (height should probably be set to 0 before animation begins?)

Attachments (0)
Change History (5)

Changed July 06, 2006 04:25AM UTC by john comment:1

priority: minorcritical

Changed July 11, 2006 08:00PM UTC by contact@cody comment:2

I have also noticed a flicker, on FF only both Mac and Windows, when using the slideDown() on an element that has the CSS display property set to none. You can see this flicker on the ThickBox demo page when a ThickBox is opened.

Changed July 14, 2006 10:34AM UTC by Brice Burges comment:3

I confirm this bug. It also seems to "flicker" in (@ end of animation).

Here's some example HTML:

<div style="position: relative; width: 100%; z-index: 1;">

<a id="personalize" href="#">{t}Add Personalization{/t}</a>

<div id="selectField" style="z-index: 2; display: none; position: absolute; top: -5px; left: -5px; width: 90%; background-color: #e6eaff; padding: 7px; border: 1px solid;">

filler... filler <br>

filler... filler (to slide up/down) <br>




$("#personalize").click(function() {


return false;


<span style="font-weight: bold;">{t}Add Personalization{/t}: </span>

<span class="pommoHelp">



<hr style="clear: both;">


Changed July 14, 2006 10:48AM UTC by Brice Burges comment:4

Some other ODD behaviour -->

If you run slideUp() on an element. Then run it again (run slide up on an element twice), slideDown() will cease to function. On the other hand, you can run multiple times on an element and a call to slideUp() will still function as normal.

Changed July 17, 2006 03:49AM UTC by john comment:5

resolution: → fixed
status: newclosed

This problem has been resolved and is in SVN.