Closed Bug 263481 Opened 20 years ago Closed 20 years ago

download manager: progress dialog box: open file and show file buttons do not work.

Categories

(SeaMonkey :: Download & File Handling, defect)

x86
Linux
defect
Not set
trivial

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: bdeit2000, Unassigned)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a5) Gecko/20041007
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a5) Gecko/20041007

linux red hat ws: download progress dialog box "SHOW FILE LOCATION" "OPEN FILE"
buttons do not work. 
mozilla build ID: 2004100706
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a5) Gecko/20041007

Reproducible: Always
Steps to Reproduce:
1 change downlaod preference to "open a progress dialog" 
2.download any file. 
3.

Actual Results:  
when done the open and show file location buttons do not work  

Expected Results:  
open should have opened the file 
show should have opened the file location in a seperate file manager.

the show file location button does work in the download managers menu bar. if
you want a work around.
Summary: download manger: progress dialog box: open file and show file buttons do not work. → download manager: progress dialog box: open file and show file buttons do not work.
Those buttons are disabled, aren't they?  That's precisely because they don't
work on Linux....
yeah, the buttons are disabled for me...

Barry, what is browser.download.progressDnldDialog.enable_launch_reveal_buttons
set to? check in about:config (have you maybe changed that setting manually?)
Product: Browser → Seamonkey
this worksforme with linux trunk 20050409
can you respond to comment 2?
(In reply to comment #2)
> yeah, the buttons are disabled for me...
> 
> Barry, what is browser.download.progressDnldDialog.enable_launch_reveal_buttons
> set to? check in about:config (have you maybe changed that setting manually?)

they were set to false. 
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.