Open Bug 384004 Opened 17 years ago Updated 2 years ago

Wrong helper app shown in pre-download window (because I changed the file type association)

Categories

(Firefox :: File Handling, defect)

x86
Windows XP
defect

Tracking

()

UNCONFIRMED

People

(Reporter: hannodv, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a6pre) Gecko/20070610 Minefield/3.0a6pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a6pre) Gecko/20070610 Minefield/3.0a6pre

When clicking on a file with an extension associated with an installed program, such as .doc and .zip files, the dialog box asking whether to save the file or open it, displays the default program to open the file, and not program currently associated with the file type.  

However, the currently associated program correctly opens the file.

The problem occurs when I change the program associated with the file in the windows xp control panel/folder options window under the file types tab from the default application to another one.

Example: I changed the application to handle .doc files from the Microsoft Office Word Viewer to Openoffice.org.  The download window's open function displays the application used as the MS word viewer, but it is opened by openoffice.org.

Windows shows an option in the file types window to restore the application used to the original(word viewer).

Reproducible: Always

Steps to Reproduce:
Discribed in the 'details' section
Actual Results:  
Discribed in the 'details' section


The bug occurs on both versions of Firefox that I have installed, Firefox 2.0.0.4 and 'Minefield' 3.0a6pre
Component: Download Manager → File Handling
Product: Firefox → Core
QA Contact: download.manager → file-handling
Summary: Application for opening files incorrectly identified in pre-download window → Wrong helper app shown in pre-download window (because I changed the file type association)
Version: unspecified → Trunk
Product: Core → Firefox
Version: Trunk → unspecified
Severity: minor → S4
You need to log in before you can comment on or make changes to this bug.