Side navigation
#3585 closed bug (invalid)
Opened November 09, 2008 11:18AM UTC
Closed February 15, 2009 11:42PM UTC
Last modified March 14, 2012 06:29PM UTC
fadeOut incorrectly sets display:none
| Reported by: | wichert | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 1.3.2 | 
| Component: | effects | Version: | 1.3.1 | 
| Keywords: | Cc: | wichert, flesler | |
| Blocked by: | Blocking: | 
Description
fadeOut is document to only set modify the opacity. However a test with jQuery 1.2.6 shows that after having animated to an opaicty of 0 it sets a display:none on the element(s), which has many undesirable side effects.
Attachments (0)
Change History (6)
Changed November 10, 2008 02:39PM UTC by comment:1
| cc: | → wichert, flesler | 
|---|
Changed November 10, 2008 09:59PM UTC by comment:2
I don't see how display: none is undesirable. I think this is the most commonly expected behavior.
Changed December 05, 2008 02:58PM UTC by comment:3
You can work around this feature by using fadeTo("fast", 0);
This will fade the element, and set visibility to hidden, however it will leave 'display' intact and thus wont disrupt the flow of your document
Changed December 05, 2008 03:00PM UTC by comment:4
However it works though, please can we update the api docs for fadeIn/fadeOut?
They do say it only affects opacity, and a brief google shows quite a few people are falling foul of the same assumption
Changed January 11, 2009 03:11AM UTC by comment:5
I would think fadeOut sets display: none because otherwise the element would pass the :visible test. Or is it a bug that opacity: 0 is :visible?
Changed February 15, 2009 11:42PM UTC by comment:6
| milestone: | 1.3 → 1.3.2 | 
|---|---|
| resolution: | → invalid | 
| status: | new → closed | 
| version: | 1.2.6 → 1.3.1 | 
This is definitely the intended behavior - and the docs are up to date, as well.
I agree. Can you post about this to the jQuery dev group ?