180344 - A freeze can occur when opening a file using "Launch File" from the Download progress dialog

Status: RESOLVED WONTFIX

(Core Graveyard :: File Handling, defect)

Description

[Chris Petersen]

Build: 2002-11-15-08
Platform: OS 9.2 
Expected Results: File should be launched by Stuffit Expander
What I got: I get a message in Finder stating "The Finder needs your attention".
However,  I can't switch out to Finder or quit Mozilla and it appears to be in a
frozen state.


Steps to reproduce:

1) Go to url. Scroll page down to Downloading Tests section.
2) Click on one of the following links:

 test-ball1.tar
 test-ball2.tar.gz
 test-ball3.zip

3) Specify Save to disk instead of using the Helper application (Stuffit). Click
OK. 

4) Specify file name and save file.

5) After file has been transfered, click on 'Launch File' button.

6) The finder displays message but user can't switch to finder or quit Mozilla.

Comment 1

[Chris Petersen]

Also happens on branch build 2002-11-12-13 1.0 under OS 9.1 and 9.2.

Comment 2

[Chris Petersen]

In this situation, I can force quit Mozilla. I do notice that an alert appears
in Finder that states "The document "file" could not be opened, because the
application program that created it could not be found"

Comment 3

[sairuh (rarely reading bugmail)]

->steve, but punt as needed.

chris, out of curiosity, did this occur with 7.0rtm or with a current trunk build?

Comment 4

[Chris Petersen]

Yes, it occurs on the latest OS 9 trunk build too. Didn't get a change to try in
NS 7 RTM.

Comment 5

[Steve Dagley]

Mac OS Classic bugs begone

Comment 6

[Simon Paquet [:sipaq]]

This bug is targeted at a Mac classic platform/OS, which is no longer supported
by mozilla.org. Please re-target it to another platform/OS if this bug applies
there as well or resolve this bug.

I will resolve this bug as WONTFIX in four weeks if no action has been taken.
To filter this and similar messages out, please filter for "mac_cla_reorg".

Comment 7

[Martin Creutziger [:MMx]]

I cannot confirm this behaviour in MacOS X with a recent build.
Because we are not working on anything dealing with old Mac since 1.3.1 anymore,
I mark this "WONTFIX".
In case that it reoccurs in MacOS X, please file a new bug.