Closed
Bug 599786
Opened 14 years ago
Closed 13 years ago
No filter when selecting new application versions through the file chooser
Categories
(Testing Graveyard :: ProfileManager, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: ahal, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:2.0b7pre) Gecko/20100922 Firefox/4.0b7pre Build Identifier: When selecting a new application version, any old file can be chosen. Several bad things happen as a result: 1) I once managed to get an exception when selecting a new application from the "New Profile" dialog. Unfortunately I couldn't reproduce and can't remember exactly which file it was I was trying to open. 2) Nothing happens when pressing the "Start" button. At the very least there needs to be user feedback saying the Application file is invalid. Reproducible: Always Steps to Reproduce: 1. Right click on a profile 2. Select "Firefox version" -> "Other" 3. Choose any file (Other methods of choosing Application version also valid) Actual Results: The file is listed in the Firefox versions list. Expected Results: Profile manager should only list valid application versions or the file chooser should filter out invalid files. Failing either of those, the user should be notified when trying to start an invalid application.
Comment 1•14 years ago
|
||
We definitely need to catch errors in this case. I'm not sure we should attempt to enforce, e.g., 'firefox' being part of the name of the selected file...I wonder if there are cases where a firefox binary is called something else?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 2•13 years ago
|
||
We now catch cases where the process fails to run and generate an alert.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Testing → Testing Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•