Note that there are some explanatory texts on larger screens.

plurals
  1. POHow exactly does firefox differ from ie in handling multiple (duplicate) posts?
    primarykey
    data
    text
    <p>I ran into a bug in Firefox involving some out-of-sync information on my form when using the reload button after some form data had been modified (through AJAX).</p> <p>In IE (7), refreshing always seems to re-submit the originally submitted data. So, if I load a form which is then modified through JS/AJAX and refresh, I see what I saw on the first load.</p> <p>In Firefox (4), I tend (at least in this case) to see the newer data. However, because I neglected to update certain form elements, the form seems to get re-submitted with partially incorrect data, in this case potentially bringing about serious confusion.</p> <p>My question is, what exactly is the difference between the way Firefox and IE handle re-posting? Is it documented anywhere? Is either way more standard? And what about other browsers?</p> <p><strong>Edit</strong>: It might be worth noting that Firefox also seems to re-render only certain elements (in my case a label's class changes, but not an input's disabled status). Does Firefox have special rules for how it updates the DOM when refreshing and re-POSTing?</p> <p>I checked the return from the (re)POST in FF, and confirmed that it has some unusual behavior. In the source of the return I get this bit:</p> <pre><code>&lt;label id="delSheetContainer" title="Estimate Sheets with Schedule Activities in the past may not be deleted." class=""&gt; &lt;input id="delSheet" name="delSheet" type="checkbox" tabindex="3" value="false" //Inserted note: this is where the disabled value would have been onclick="this.value=(this.value &amp;&amp; 1); bSave=true; setBtn(this.checked);" /&gt;Delete Sheet &lt;/label&gt; </code></pre> <p>But in the browser (and Firebug), I see a still-disabled checkbox. The label, however, has been properly updated. Can anybody detail this behavior as well? (references appreciated!)</p> <p><strong>Edit</strong>: As Boris explained, Firefox maintains "form state" across refreshes. My problem is actually being caused by this fact; the server is returning the right stuff, but Firefox maintains the form state anyway.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload