Skip to main content

Bug Tracker

Side navigation

#12399 closed bug (notabug)

Opened August 26, 2012 11:41AM UTC

Closed January 14, 2013 03:03AM UTC

Fade fails if target does have css3 transition properties

Reported by: ALaguna Owned by: gnarf
Priority: low Milestone: None
Component: effects Version: 1.8.0
Keywords: Cc: gnarf
Blocked by: Blocking:

Hi there,

I've just updated jQuery to 1.8.0 from 1.7.2 in one of my projects and suddenly realized that fadeIn transition weren't working good.

Basically if the target class or ID does have a CSS3 transition property for opacity it just appear or disappear but does not fade.

In the previous version, the fadeIn, fadeOut just worked fine taking the animation from the one specified in the transition.

I've prepared two jFiddles:

1.8 version:

1.7.2 version:

Attachments (0)
Change History (9)

Changed August 28, 2012 03:39PM UTC by Harry comment:1

My experience is that fadeIn works with 1.7.2, but does NOT work with 1.8.0 . My CSS is NOT using the transition property for either version.

Changed August 29, 2012 05:49AM UTC by comment:2

If you delete the CSS transition you'll see it fading

Changed August 31, 2012 12:24AM UTC by sindresorhus comment:3

cc: → gnarf
component: unfiledeffects
priority: undecidedlow

Changed August 31, 2012 11:41AM UTC by comment:4

Still reproduced in 1.8.1

Changed September 04, 2012 03:14PM UTC by timmywil comment:5

owner: → gnarf
status: newassigned

Changed September 26, 2012 11:04AM UTC by ALaguna comment:6

Still reproduced in 1.8.2

Changed January 13, 2013 08:59PM UTC by emepe comment:7

Still reproduced in 1.8.3.

Changed January 13, 2013 10:01PM UTC by mikesherov comment:8

Which is why it's still "open". Please don't bump tickets.

Changed January 14, 2013 03:03AM UTC by dmethvin comment:9

resolution: → notabug
status: assignedclosed

It might be easier to just close this wontfix. Why combine a jQuery fadeIn with a CSS transition?

In any case I suspect the problem is due to the .hide() on an element that isn't yet in the DOM. That isn't a well-defined situation.

For now I'll close this as notabug and you can make the case for why it is.