272846 - removeChild behaves oddly when dealing with nodes containing form inputs

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Gillian Kinney]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

In the linked test case, clicking an X will remove the associated
table row and recalculate the total price of all the items.  This seems to be a
simple task, but it does not execute consistently or correctly.  I've observed 
the following behavior:

- When the table row removal function is called normally, an item's price input 
gets stuck although its row has gone.
- Sometimes a form input gets duplicated when its parent row is removed.
- Inserting delays (for example, alerting the ID of the input being added to the
total) increases the likelihood that the code will execute properly, but it
doesn't always work.

This script works as expected in IE 6.  To the best of my knowledge, I am not
using any nonstandard methods.

(If the test case seems like an overly complex means of handling the task at
hand, keep in mind that it's a simplified version of an interface that I'm
working on.)

Reproducible: Always
Steps to Reproduce:
1. Type numerical values in the boxes next to the products.
2. Press the Calculate Total button.
3. Click an X next to a product.

Actual Results:  
The JavaScript calculates a new total, which is virtually always incorrect
because the form fields are not removed properly when the table rows are deleted.

Expected Results:  
It should have removed any form fields inside the element deleted via removeChild.

Comment 1

[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 2

[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.