Mozilla/5.0 (Windows NT 5.1; rv:8.0a1) Gecko/20110807 Firefox/8.0a1 Confirming
Component: General → General
Product: Firefox → Core
QA Contact: general → general
Version: 5 Branch → Trunk
Attachment #551635 - Attachment description: Source code for problem → testcase
It's not actually random; just a matter of indices shifting....
Depends on: 660549
Created attachment 552937 [details] [diff] [review] wip (wdiff) Is there a reason we don't use the ID in the state key?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Form values remembered randomly and incorrectly when insertBefore used → Form <input id> values remembered incorrectly when insertBefore used
Eric Pascarello, to improve behaviour in your case slightly, you can add "name" attributes to your inputs with the same values as your ids.
(In reply to Mats Palmgren [:mats] from comment #3) > Is there a reason we don't use the ID in the state key? Oh, I see this is being discussed in bug 660549...
This happens with INPUT[TYPE=HIDDEN] elements as well! Every time Firefox pushes a major update, I spend hours trying to figure out why a hidden input that is ONLY set on the server side and NEVER altered on the client side suddenly contains a value that NEVER should have been assigned to it, only to realize that Firefox is bungling about. The only workaround I've found is to make certain that autocomplete="off" is implemented on affected elements. (Firefox 16, Windows Vista)
Test case worksforme. Might have been fixed with bug 737851.
Yes. This got fixed on the day bug 737851 landed.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Assignee: nobody → malmasry
Target Milestone: --- → mozilla25
You need to log in before you can comment on or make changes to this bug.