eternal/endless/infinite loop when associating Firefox/SeaMonkey/Mozilla as a helper application for a given file type

NEW
Unassigned

Status

()

--
critical
16 years ago
2 years ago

People

(Reporter: chimera, Unassigned)

Tracking

(Blocks: 1 bug, {helpwanted})

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.1) Gecko/20020826
Build Identifier: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.1) Gecko/20020826

I think the download manager should either prevent the user from choosing
mozilla itself as "open with", or (better) figure out that the user wants the
file opened in the browser, not by the download manager at all.

Reproducible: Always

Steps to Reproduce:
1. download a binary file
2. choose mozilla.exe to handle file
3. uncheck the box 'always ask'
4. have fun...
QA Contact: sairuh → petersen

Comment 1

16 years ago
*** Bug 201565 has been marked as a duplicate of this bug. ***
*** Bug 214157 has been marked as a duplicate of this bug. ***
*** Bug 205826 has been marked as a duplicate of this bug. ***
*** Bug 208636 has been marked as a duplicate of this bug. ***
.
Assignee: blake → law
Severity: normal → critical
Status: UNCONFIRMED → NEW
Component: Download Manager → File Handling
Ever confirmed: true

Comment 6

15 years ago
*** Bug 215554 has been marked as a duplicate of this bug. ***

Comment 7

15 years ago
*** Bug 222833 has been marked as a duplicate of this bug. ***

Comment 8

15 years ago
*** Bug 229852 has been marked as a duplicate of this bug. ***
Assignee: law → cbiesinger
QA Contact: chrispetersen → ian
Summary: Eternal loop when associating mozilla.exe with file type → Eternal loop when associating mozilla.exe with file type as helper application
*** Bug 213316 has been marked as a duplicate of this bug. ***
*** Bug 208231 has been marked as a duplicate of this bug. ***
*** Bug 235027 has been marked as a duplicate of this bug. ***

Comment 12

14 years ago
*** Bug 264356 has been marked as a duplicate of this bug. ***
Assignee: cbiesinger → file-handling
Keywords: helpwanted
*** Bug 266598 has been marked as a duplicate of this bug. ***

Comment 14

14 years ago
*** Bug 276343 has been marked as a duplicate of this bug. ***
*** Bug 280462 has been marked as a duplicate of this bug. ***

Comment 16

14 years ago
*** Bug 295955 has been marked as a duplicate of this bug. ***
*** Bug 317670 has been marked as a duplicate of this bug. ***

Comment 18

13 years ago
*** Bug 316261 has been marked as a duplicate of this bug. ***

Comment 19

13 years ago
An enhancement would be to have an additional choice in the download window ("What should Firefox do with this file?"):

"Attempt to display file"

This would force the browser to render it internally, using whatever fallback mechanisms the browser has, ignoring MIME type.

In most cases, this will work just fine.  There's a lot of websites out there that serve content that can be seen just fine in a browser, but for whatever reason has the wrong MIME type encoded, or has the EMBED tag around it, or something like that.  This confuses the browser, and so the user can't easily open the content just by clicking on it.

If there's already a bug open for this enhancement, please link it here.

Comment 20

13 years ago
In response to comment #19: the enhancement is in Bug 196078 for text/* documents, and Bug 57342 for everything else. 
*** Bug 351223 has been marked as a duplicate of this bug. ***
Duplicate of this bug: 379545
Summary: Eternal loop when associating mozilla.exe with file type as helper application → eternal/endless/infinite loop when associating Firefox/SeaMonkey/Mozilla as a helper application for a given file type
Duplicate of this bug: 461691
Duplicate of this bug: 463361

Updated

10 years ago
Duplicate of this bug: 476774
Duplicate of this bug: 476774

Updated

10 years ago
Duplicate of this bug: 477524
Duplicate of this bug: 478349
Assignee: file-handling → nobody
QA Contact: ian → file-handling

Comment 29

9 years ago
Would it not be possible to detect that the file open request came from the OS (command line parameter) and not defer to helper applications in that case, ie. error message.

Trying to detect the source or destination seems foolhardy.

(I'm not sure if this is the right bug. Bug 218257 Bug 215554 are newer.)
Maybe, but the problem is of course that the code that does the helper app launching doesn't know that the URL came from the command line, so this would require quite a bit of code changes.
Duplicate of this bug: 595472
Duplicate of this bug: 613136
Duplicate of this bug: 613136

Updated

8 years ago
Duplicate of this bug: 628138
Duplicate of this bug: 629641
Oh guys, I'm so sorry this was a dupe. I really did look at the list given and used the keywords of ".do open file" and "infinite loop" to try to find it but there was a list SOOOO long and it was definitely not in the first 100 that came back. I don't mean to fill up the system with dupes, but it sure would be nice to have this fixed! Thank you for checking it out. :) Your work on this browser is VERY appreciated!! Firefox is the best!
Duplicate of this bug: 638715
Duplicate of this bug: 654681
Duplicate of this bug: 668713
Duplicate of this bug: 771982
Duplicate of this bug: 776335
Duplicate of this bug: 776335
Duplicate of this bug: 852239
This bug is like an easter egg! 10 years old, critical but most people probably don't hit it ;) I hit it trying to open PDFs, it wasn't opening in Aurora so I tried choosing Aurora. It worked for the first PDF I tried it on, then the 2nd one looped :D At least the browser was responsive and I could exit (yay session store!)

Updated

4 years ago
Duplicate of this bug: 1077889
Duplicate of this bug: 1133217
Duplicate of this bug: 977653

Updated

3 years ago
Duplicate of this bug: 1178310

Updated

3 years ago
Duplicate of this bug: 1148976
Duplicate of this bug: 1156335
Comment hidden (spam)

Updated

2 years ago
Component: File Handling → File Handling
Product: Core → Firefox
Version: Trunk → unspecified

Comment 52

2 years ago
I'm curious why we still allow FF to select itself and loop in such a way, especially considering how easy it is to do and it can effectively brick the profile (and system if it has low resources).
You need to log in before you can comment on or make changes to this bug.