Closed Bug 1608012 Opened 5 years ago Closed 5 years ago

Firefox suggests opening downloaded files as file:// URI if explorer.exe isn't running as login shell

Categories

(Firefox :: File Handling, defect)

68 Branch
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: bugs123, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0

Steps to reproduce:

  1. Terminate explorer.exe and launch firefox; or use shell replacement such as bbLean.
  2. Download a file, go to Downloads section, click on the downloaded file.

Actual results:

"Launch Application" dialog is shown, listing "file link" as a filetype.

Expected results:

File should open in the default application assigned by Windows.

Hi

I tried to replicate the issue using windows10 64bit and the latest Firefox Nightly release 74.0a1
What i did was to terminate explorer.exe and in CMD i executed Firefox nightly
Then i did a search for "DOWNLOAD RAR EXAMPLE", entered one of the links, downloaded a rar file and i was able to open it.

What kind of file did you download when you had the problem? can you share the link?

Also Please download the latest Firefox Nightly release from here: https://nightly.mozilla.org/ and retest the problem.

If you still have the issue please create a new profile, you have the steps here:https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles?redirectlocale=en-US&redirectslug=Managing-profiles#w_starting-the-profile-manager

Lastly test if the issue is reproducible in safe mode, here is a link that can help you:
https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode

Regards
Pablo

Component: Untriaged → File Handling

Hello

Happens with every file, doesn't matter the extension.
I just tried nightly 74.0a1, it indeed works as intended there, clean profile or not.
Affected versions seem to be 68.3.0esr; 68.4.0esr; 68.4.1esr; and current stable version.

Fixed in 68.4.2esr. You can close this issue.

Resolving per comment #3; I suspect this got fixed by bug 1602726.

Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
See Also: → 1602726
You need to log in before you can comment on or make changes to this bug.