Ok, finally we found out what caused this behaviour. Fortunately, it
can easily be fixed.

This is the ticket regarding the issue:
http://dev.jquery.com/ticket/4374

And here's the fix for it:
http://dev.jquery.com/changeset/6282

Regards,
Andy

On 24 Mrz., 15:50, Thag <[email protected]> wrote:
> We have an application that opens sections (div) of a webpage and
> fills it with the content of an AJAX response by the server.
> It all worked fine with IE6 and FF3 until we upgraded to JQuery 1.3.2
> (were using 1.3 before). It still worked in IE6, but FF couldn't close
> the section (slideUp) anymore.
>
> This is the code of the AJAX-request: the div is "opened" and its
> content is shown. This did work in 1.3 and still does in 1.3.2 for
> both FF and IE6:
>
> $.post(sectionAction, function(data){
>                         $("#content").html(data);
>                         $("#content").slideDown("slow");
>                   });
>
> Because we do only issue a request the first time a user opens a
> section, the visibility of the content div is afterwards triggered 
> viaslideUp/slideDown. Here's the code:
>
> if ($("#content").is(":hidden")) {
>         $("#content").slideDown("slow");} else {
>
>         $("#content").slideUp("slow");
>
> }
>
> All of the above worked perfectly until we upgraded to 1.3.2. The
> effect in FF was that you could see the div close smoothly but pop
> open again after being closed.
> Debugging with some JS alerts and Firebug, we found out that the check
> for :hidden in the if above didn't return the right status of the div
> and therefore always entered the first branch of the if.
>
> A second effect was that once we changed the is(:hidden) check to css
> ("display") == "none", the second branch of the if was executed, but
> nowslideUpdidn't do anything to the div.
>
> As we read in the release notes, a change to :hidden was made in
> 1.3.2, which should not be a problem. It looks likeslideUp/slideDown
> are not "updated" in 1.3.2 according to the new logic.
>
> We now downgraded to JQuery 1.3 again.
>
> Thanks,
> Andy
>
> On 4 Mrz., 21:29, John Resig <[email protected]> wrote:
>
> > Not sure - do you have some sample markup?
>
> > --John
>
> > On Wed, Mar 4, 2009 at 2:17 PM, botskonet <[email protected]> wrote:
>
> > > I've been using the following code in an app since jQuery 1.2 and it's
> > > been working fine. However, with an upgrade to 1.3.2 (1.3.1 worked)
> > > this line no longer actually performs:
>
> > > $('#news-area').animate({opacity: 'hide', height: 'hide'}, 'slow');
>
> > > also tried
>
> > > $('#news-area').slideUp();
>
> > > I've verified that the element exists, and $('#news-area').hide();
> > > behaves just fine. Doing the reverse of show/slideDown works just fine
> > > on the same element.
>
> > > Is there something in 1.3.2 that could have broken this?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"jQuery Development" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/jquery-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to