This project is archived and is in readonly mode.

#220 ✓invalid

Same .fade(0) behaving differently across browsers.

Reported by Jared | July 14th, 2008 @ 07:04 AM | in 2.0 (closed)

I set up a little thing over here

It's an extremely simple .fade(0); effect with a couple day old version of the full Core and More builds.

It works fine in Safari and Firefox 3, but not in FF2, IE6, or IE7. Maybe others, I haven't tried Opera or Konqueror yet.

This bug may have to do with the absolute positioning used.

Comments and changes to this ticket

  • Jan Kassens

    Jan Kassens July 14th, 2008 @ 11:52 AM

    • State changed from “new” to “open”
    • Assigned user changed from “Valerio” to “Jan Kassens”


  • Jan Kassens

    Jan Kassens July 15th, 2008 @ 11:48 AM

    seems like a browser bug, i've stripped it down a bit further:

    Firefox only updates the opacity on load and when the element is rerendered (i.e. tab switch back and forth, or hovering the element in the firebug dom explorer).

    Probably this is unfixable...

  • Jared

    Jared July 15th, 2008 @ 03:35 PM

    The weird thing is that if it is fade(0), it does work in IE6, except instantly (no actual fade, just changes the opacity). However, if it is a non-integer value like .2, it doesn't work at all.

    So it can update to some extent.

    Maybe if fade() did something with filter:alpha(opacity=value) also?

  • Jared

    Jared July 15th, 2008 @ 03:38 PM

    Oh wait, nevermind, that won't help at all.

  • Jared

    Jared July 15th, 2008 @ 03:53 PM

    What I found out is that if you have the fade applied to both divs, they fade, but not together. Is there any way to make to .fade effects happen simultaneously.

  • Jared

    Jared July 15th, 2008 @ 04:10 PM


    I updated it to have a fade on the picture inside the div and the other div with nothing on the parent div, and it works in IE6, too.

  • Jan Kassens

    Jan Kassens November 21st, 2009 @ 02:56 PM

    • Tag changed from 1.2, defect, fade, firefox, website to defect, fade, firefox
    • State changed from “open” to “invalid”

    if anyone has a fix for that, add it here. I'm closing this ticket for now, since it seems like a non-fixable, extremely rare bug.

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

Shared Ticket Bins

People watching this ticket