221712 - Re-writing a later disables all access to that form element

Status: RESOLVED EXPIRED

(Core :: DOM: Core & HTML, defect)

Description

[Anthony Swan]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030210
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030210

When you re-write a div (the innerHTML property of the div), any forms included
on that are not re-bound to the javascript DOM.   The form submits properly if
you manually change the value but if you change it programmatically the value
reflects the newly changed value, but the form submits the value in the field.
It appears that this is a one way issue: if you change the value manually,
alerting the value with javascript works as does alerting the value after
changing it with javascript, but the form does not change to reflect the new
value and the old value is submitted to the CGI.

Reproducible: Always

Steps to Reproduce:
1.Create a simple page with a form on a div
2.use innerHTML to rewrite the div
3.use javscript to set the new form field value
4.use javascript to alert the new form field value
5.submit the form

Actual Results:  
The form is submitted with the value in the field, but not the value that was
placed in there by javascript

Expected Results:  
The form field should be updated to the value set in the javascript.

Works in Netscape 7.0.x, does not work in Netscape 7.1+
Does not work in Mozilla 1.3, 1.3b, 1.4 or 1.5

Comment 1

[Anthony Swan]

Attachment: A HTML test case for this.

This is an html test case.  You can test part of the functionality.  To test
the full functionality create a simple program that outputs all the posted data
and see what the browser submits.

Comment 2

[Boris Zbarsky [:bzbarsky]]

Anthony, could you give step-by-step instructions as to what I should do with
that testcase to reproduce the problem?  What is the expected result after those
steps?

Comment 3

[Gervase Markham [:gerv]]

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/

Comment 4

[Gervase Markham [:gerv]]

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.