324377 - [FIX] Submitting file control that's just been added to the DOM fails

Status: RESOLVED FIXED

(Core :: Layout: Form Controls, defect, P3)

Description

[Arpad Ray]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1

When cloning a file input (with an existing value) from a form in one document to another (eg. to a form in an iframe), submitting the form using the submit() method causes the file input to lose its value. Its name persists but the filename and data don't.

If the form is submitted manually with a submit button, it works perfectly.

Reproducible: Always

Steps to Reproduce:
1. Enter a file into a file input
2. Use cloneNode to append it to a form in another document
3. call the submit() method on that form, rather than clicking the submit button

Actual Results:  
The element name is sent, but the filename is blank and there's no data.



Expected Results:  
The element should be sent as normal.

Example output: (two form values and the file)
-----------------------------214762178421665
Content-Disposition: form-data; name="aupload_file_id"

d41d8cd98f00b204e9800998ecf8427e
-----------------------------214762178421665
Content-Disposition: form-data; name="aupload_file_name"


-----------------------------214762178421665
Content-Disposition: form-data; name="myfile"; filename=""
Content-Type: application/octet-stream


-----------------------------214762178421665--

Comment 1

[Boris Zbarsky [:bzbarsky]]

Attachment: Patch

So the actual issue here (based on debugging Arpad's testcase) is that we're submitting before initial reflow of the file control frame, and that can't get the value off the mTextFrame until it sets it... in initial reflow.  The cross-document thing and the cloneNode thing are incidental -- you could get the same effect with some style toggling on a single file input in the DOM.

Comment 2

[Boris Zbarsky [:bzbarsky]]

roc, I realize that for 1.9 we'll try to nix the whole textfield thing, but I think this might be a good change for 1.8.1 too...

Comment 3

[Robert O'Callahan (:roc) (email my personal email if necessary)]

Comment on attachment 209331 [details] [diff] [review]
Patch

I agree with your XXX comment. Seems like textControl.value should always work.

Comment 4

[Boris Zbarsky [:bzbarsky]]

Attachment: What I checked in

I made this always use mTextControl.

Comment 5

[Boris Zbarsky [:bzbarsky]]

Er, I meant mTextContent.  In any case, fixed.