We’re seeing that the 2.0.0.2 release of FireFox has a behavior change that’s affecting ASP.NET AJAX. 

Basically the dynamically loaded scripts seem to now execute asynchronously, which causes them to fire after the inline scripts, whereas previously they’d fire as soon as they were added to the DOM. 

This will affect scenarios where a component relies on PageRequestManager events inside of an UpdatePanel. For example the ModalPopup control that is part of the Control Toolkit.

We are actively working with the Firefox team to figure out the best approach to address this issue and we will update this thread as soon as we know something

Im having problems with the ajax toolkits tabcontrol, and wanned to hear if you were any closer to finding a solution to the problem

Bump.  :o)  Any update to speak of?  I'd really hate to put in a work-around (ie:  the window.setTimeout(......)), but I'd like to have a clearer understanding of the timelines regarding the resolution of this issue.

 Can anyone please provide an update?

Thanks,
Greg

We are still talking to the Firefox team.. It is taking longer that we expected.

 

AdnresS

Consider using jQuery, a very lightweight Javascript library which has a feature to help here. Look up the ready function.

http://docs.jquery.com/Tutorials:Introducing_%24%28document%29.ready%28%29

It will run the given function once the page is ready, meaning once the markup has been loaded. And it precedes the images and other media being loaded. I am now using it with my ASP.NET websites, like LinkMindr.com. 

 $(document).ready(function() {
   // put all your jQuery goodness in here.
 });

  

 

 

 

This sounds promising.  How does this interaction work with ASP.net AJAX?  Are there any conflicts in using both libraries? 

I am about 95% done with development on my application, which relies heavily on the MS AJAX framework.  I would hate to bring in a new component and have it break everything else.  :o)

Thanks,
Greg

I have not had any issues with jQuery and ASP.NET together. Here is an example site I put together recently which makes use of ASP.NET AJAX and Thickbox which is built on jQuery.

http://homes.offwhite.net/UnionPointLofts.aspx

The collapsible panels are near the bottom while the Thickbox feature manages the images. You can see there are no conflicts.

I use jQuery much more extensively on this site...

http://www.linkmindr.com/

It also uses the collapsible panels while I use jQuery to do my lightweight callbacks. Since the ASP.NET AJAX objects are generally all under the Sys name they will not conflict with other libraries which maintain a similar namespace concept. And jQuery is respectful of this construct. The following blog entry was written by the author of the jQuery library and the topic should reassure you about using jQuery.

 http://ejohn.org/blog/thoughts-on-openajax/

 

 

I don't know if this is the same issue but FireFox guys seem to work on fixing the delayed javascript evaluation: https://bugzilla.mozilla.org/show_bug.cgi?id=371576

Anyone have an update on this issue?

 

We have being actively communicating with the FireFox team to address this issue.  We believe that Mozilla Bug 371576 addresses this issue.  They’ve got a fix and are working on an update release.

Thanks

AndresS

 

I have problem with Firefox too. I copy PopupControl sample from ajaxtoolkit to try out. If I move the <asp:UpdatePanel> from inside of <asp:panel> to outside of <asp:panel>, the popup panel refresh for each callback event. It won't close popup when server issues commit(). It happens not only in Firefox 2.0, it's not working in Firefox 1.5.0.10 either. But same code works in IE. It looks like all those elements in the popup panel are re-created for each callback events.

In one of my production applications we use a ModalPopup that's invoked from a gridview control specifically a imagebutton. In 1.5.0.10 it works great. Confirmed that it shows nothing in version 2.0.0.2 clicking the imagebutton just puts up the progressupdate for a few seconds and then disappears. And I just confirmed that release 2.0.0.3 fixed it.

ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2007-03-09-19-firefox2.0.0.3

They haven't realeased it officially yet it looks like... (as in pushing down the update) but this will fix the issue. Time to start letting users know that they need to stay up wit the latest versions.

JoeWeb

Hi all - please download the latest Firefox 2.0.0.3 candidate build from this directory and see if the issue is resolved -ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2.0.0.3-candidates/rc1. This build includes the bug fix for https://bugzilla.mozilla.org/show_bug.cgi?id=371576.  Please let us know ASAP if you still see issues with this candidate build. You can email me directly at marcia@mozilla.org. Thanks!

Good job, the 2.0.0.3 fixes my problem on modalpopupextender

Thanks

Seems to fix the issue I was experiencing as well... Has anyone seen anything about when the RC will be released?