Closed Bug 369500 Opened 18 years ago Closed 15 years ago

Ajax gets old form values when reloading page, and not when entered as a new url.

Categories

(Firefox :: General, defect)

2.0 Branch
x86
Windows 2000
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: vide.wiberg, Unassigned)

References

()

Details

(Whiteboard: [CLOSEME 5-15-2010])

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1 The code on the page is built to update the other button text (button 1 updates button 2 and the other way around). This works fine in IE6 and Opera9, however in FF2 this does not work. Reproducible: Always Steps to Reproduce: 1. Enter address: http://dev.webreport.se/AjaxToolkit/ajaxtoolkit.aspx 2. Click both buttons on the page, they should now have the text of current date and time. 3. Reload the page by either CTRL+R or right click and "reload". 4. Click one of the buttons, this now updates both buttons. Actual Results: The button clicked gets its last value (incorrect, it should stay as it was), and the other one gets the new date and time (correct). Expected Results: The button clicked should not change, the other button should get the new date and time. HTML source: <%@ Page Language="C#" AutoEventWireup="true" CodeFile="ajaxtoolkit.aspx.cs" Inherits="test_ajaxtoolkit" %> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" > <head runat="server"> <title>Untitled Page</title> </head> <body> <form id="form1" runat="server"> <div> <asp:ScriptManager runat="server" ID="SM" /> <asp:UpdatePanel runat="server" ID="UP1"> <ContentTemplate> <asp:Button runat="server" ID="btn1" Text="Click me" OnClick="btn1_click" /> </ContentTemplate> </asp:UpdatePanel> <asp:UpdatePanel runat="server" ID="UP2"> <ContentTemplate> <asp:Button runat="server" ID="btn2" Text="Click him" OnClick="btn2_click" /> </ContentTemplate> </asp:UpdatePanel> </div> </form> </body> </html> Code source: using System; using System.Data; using System.Configuration; using System.Collections; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Web.UI.HtmlControls; public partial class test_ajaxtoolkit:System.Web.UI.Page { protected void Page_Load( object sender, EventArgs e ) { } protected void btn1_click( object sender, EventArgs e ) { btn2.Text = "1: " + DateTime.Now.ToString(); } protected void btn2_click( object sender, EventArgs e ) { btn1.Text = "2: " + DateTime.Now.ToString(); } }
Also related to this report: After chaging the values on the controls by clicking the buttons, the controls assume the correct values. After this, if you refresh the page (just F5), the values on the controls become the values these controls had on the first time the page was loaded. But if instead, or afterwards, you press Ctrl+F5 (force full refresh?), the page refreshes and the values on the controls become the ones they should be.
This bug was reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.3 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME http://www.mozilla.com http://support.mozilla.com/kb/Managing+profiles http://support.mozilla.com/kb/Safe+mode
Whiteboard: [CLOSEME 5-15-2010]
Version: unspecified → 2.0 Branch
No reply, INCOMPLETE. Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.