Closed Bug 254153 Opened 19 years ago Closed 18 years ago
Form contents deleted / erased / reset after a Back, depending on <input> elements placement
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040413 Debian/1.6-5 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040413 Debian/1.6-5 Depending on where you place the input elements of a form, after you submit it and then push the back button, some field contents are lost. This happens for example when you have your <form> and some <input> tags inside a <table> but outside a <tr> or a <td>. I tried to create the smallest possible HTML code that reproduces this bug, please see the URL above. Reproducible: Always Steps to Reproduce: 1. Go to the example URL that I have given above 2. Write anything in the two fields and hit the Send button 3. On the resulting page, then push the Back button Actual Results: The contents of the second field is deleted (reset to blank). The first field is intact however. Expected Results: The contents of the second field should remain as it was before I submitted the form. Problem also occurs when one or both of the fields are type="hidden". However, when the first input element is not present, this problem does not occur. Also does not occur when all input elements are at the same nesting level, e.g. all in <td>.
ok, your html is of course invalid, but that's fine, nobody writes valid html anyway, people just put random text with < and > and characters inside on the net, and hope browsers render something that remotely resembles what they expect. the <input> inside the <table> gets moved before the <table> because it is not allowed where you have put it. I'm not sure why the form stays where it is, because it isn't allowed there either. I'm especially not sure why the text does not get remembered, in the input inside the <td>...
> I'm not sure why the form stays where it is, because it isn't allowed there > either. Because if the form moves pages that wrap rows or cells in forms would break.... This is a duplicate.
*** This bug has been marked as a duplicate of 246692 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Reopening. The bug this got marked a dup of may or may not be the same issue... This is a duplicate of a different bug.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
*** Bug 254164 has been marked as a duplicate of this bug. ***
Note bug 288462.
Could this be a dupe of bug 285730?
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago → 18 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.