360986 - FireFox does not undo changes to RadioButton when user hits Back button

Status: RESOLVED INVALID

(Firefox :: General, defect)

Description

[Gili Tzabari]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0

I have three forms in a page. The first form contain two radio buttons. Depending upon which radio button is selected, either form2 or form3 is displayed. All this logic is all implemented on the server-end so it involves posting a request every time the user changes his selection in form1.

Here is how I reproduce the bug:

1) form1: [x] [ ]           form2
2) form1: [ ] [x]           form3
3) Hit Back Button
4) form1: [ ] [x]           form2

I am expecting step 4 to read:

4) form1: [x] [ ]           form2

   It looks as if FireFox rolls back the state of the bottom form, but not the top one. This works properly under IE6.

Reproducible: Always

Comment 1

[Gili Tzabari]

BTW, I can't post the actual HTML file for security reasons because it is an Administration page on my company's intranet. Sorry ;)

Comment 2

[Dave Townsend [:mossop]]

Firefox is simply remembering the exact state of the page as you left it.

See http://developer.mozilla.org/en/docs/Using_Firefox_1.5_caching for ways to handle this if necessary.

Comment 4

[Ryan]

> Firefox is simply remembering the exact state of the page as you left it.

The page source is NOT being cached, if I "view source" and look at the HTML, I can see its coded to have the first radio button selected (for example), yet Firefox is showing the second radio button selected.  You say his is normal behavor, its just "remembering" for me what I had set it to previously?  Thats crazy - Firefox should render HTML as its given!

Comment 5

[Ryan]

How can I petition to get this bugs status changed from RESOLVED INVALID?  Every person I've showed this to thinks its a bug.  I like Firefox but its hard to get it used in the workplace when it screws up web applications by not indicating the correct radio button.  -thanks.

Comment 6

[Ryan]

This bit me again today, wasted a few hours of time trying to debug a web application where the radio buttons in the admin area were not reflecting the correct changes made on the front end.

It was because of this BUG.  I thought FF was popular amoung developers?  How can it be when it doesn't not render the HTML properly?

Comment 7

[Dave Townsend [:mossop]]

It renders the page exactly as specified when the page is loaded. But going back to the page does not reload it shows the page as it was when the user left the page. The URL I gave gives both javascript and simple html methods to indicate that you want the page to be loaded from scratch everytime the user goes back to the page.

Comment 8

[Ryan]

Dave I understand what you are saying - and indeed a Ctrl+F5 does cause it to display the correct selected radio button.

But a simple refresh of the page (not using Ctrl+F5) refreshes ALL the other form fields.  When I view source, the HTML clearly indicates that the first radio button should be selected, but instead the second one is selected until I do a Ctrl+F5.   There is a bug here - your statement "It renders the page exactly as specified when the page is loaded" is false.

Comment 9

[Dave Townsend [:mossop]]

(In reply to comment #8)
> Dave I understand what you are saying - and indeed a Ctrl+F5 does cause it to
> display the correct selected radio button.
> 
> But a simple refresh of the page (not using Ctrl+F5) refreshes ALL the other
> form fields.  When I view source, the HTML clearly indicates that the first
> radio button should be selected, but instead the second one is selected until I
> do a Ctrl+F5.   There is a bug here - your statement "It renders the page
> exactly as specified when the page is loaded" is false.

You simply are not understanding when pages are loaded and when they are merely re-rendered.

When you visit the page for the first time it is loaded and the html is displayed as-is.

When you go back to the page using the back button the page is not loaded. Instead the pages state as it was when the user left the page is re-rendered so it should look identical to how it did when the user browsed away from the page.

View source shows the source html, not the pages current state, for that you would need to use the DOM inspector or "View selection source" in the context menu.

Comment 10

[Ryan]

I am hitting 'Reload' (Ctrl+R), not simply going back in my history.  When I do this, all the other fields on the form update with current information from the database.  The radio buttons, however, do not.  Even though I view the *new* html source (acquired when I hit Ctrl+R) it shows 'checked' by the first radio button - FF still shows only the second radio button as selected, since that is what was selected before I refreshed the page.

Comment 11

[Dave Townsend [:mossop]]

Then what you are seeing differs from this bug report in an important way. Please file a new bug with an accurate description of what you are seeing.

Comment 12

[Ryan]

Attachment: Test case to demonstrate FF radio button bug

Instructions: Load the page in FireFox.  Note the text field value, and the fact that the first radio button is selected.

Then edit the source, changing the value of the text field to "updated" or whatever you like.  Also remove the "checked" attribute from the first radio button, and place it into the second radio button.

Refresh the page in FireFox.  Note that the text field correctly displays the update value.  The radio button, however, has failed to change.  The first radio button is still selected, even though the HTML source is indicating that the second button should be the one that is selected.

Comment 13

[Ryan]

Comment on attachment 314956 [details]
Test case to demonstrate FF radio button bug

<?xml version="1.0"?><html><head><title>FF radio button test</title></head><body>

  

  <form>

  Field 1:<input value="test value 1"/><br/><br/>

  

  Radio A<input type="radio" checked/>

  Radio B<input type="radio"/>

  </form>

  

</body></html>

Comment 14

[Ryan]

Ignore comment 13, I didn't mean to do that.

I've already submitted this as a separate bug, but it was marked as a duplicate of the bug we are currently commenting on.

Here was my original submission:
https://bugzilla.mozilla.org/show_bug.cgi?id=391238

Is that adequate or should I resubmit?

Comment 15

[Dave Townsend [:mossop]]

Just reopen your original bug.