487423 - upload localfile doesn't close the file properly

Status: RESOLVED DUPLICATE of bug 479778

(Firefox :: General, defect)

Description

[dlorre]

User-Agent:       Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.0.8) Gecko/2009032609 Firefox/3.0.8 (.NET CLR 3.5.30729)

When I upload a file with Firefox/Windows, I can't delete the file afterward without closing firefox. The issue doesn't appear with internet explorer.

Reproducible: Always

Steps to Reproduce:
1.Upload a localfile to a site
2.try deleting the file (doesnt work)
3.close firefox (now you can delete the file)
Actual Results:  
I can delete the file once I have closed Firefox

Expected Results:  
I should have been able to delete the file with Firefox opened.

suggestion : fclose(filehandle) ;


It's a very annoying bug which will affect anyone uploading updates repeatedly with Firefox (using IE 7 now).

Comment 1

[Jo Hermans]

see bug 183689 - it can come from the Firebug extension (bug 479778), or the LiveHTTPHeaders extension. The basic problem is probably bug 459384.

Comment 2

[Boris Zbarsky [:bzbarsky]]

Gah.  Please do NOT dup bugs to other bugs unless you know they're duplicates.  Given that the steps to reproduce do not include any history navigation, this is VERY unlikely to be a duplicate of bug 459384.  It's pretty likely caused by one of the extensions installed, but it might also be something else.

If you think the bug might be related but not a duplicate, the right thing to do is to mark it dependent, not to duplicate.

Reporter, are you using either of the above extensions?

Comment 3

[Jo Hermans]

Boris, I was the one that filed bug 183689 in the first place, but it highjacked for lots of different things (mainly the Firebug and LifeHTTPHeaders problems), and was duped by you to 459384. I'm only doing what you have done.

Comment 4

[Boris Zbarsky [:bzbarsky]]

Jo, I just dupped it to a bug that didn't have the hijacking in it and was specifically filed to treat your issue in a clean way so it could actually be fixed.  The hijacking is not a good thing, by any means, and I'm not happy that it had to be worked around.

But this bug really doesn't sound like it's about the same issue, since there is no mention of reload or going back in history in the summary.

Comment 5

[dlorre]

I confirm that it comes from Firebug, disabling Firebug solves the issue.

Comment 6

[Boris Zbarsky [:bzbarsky]]

Thanks for checking!