Closed Bug 151320 Opened 23 years ago Closed 23 years ago

"Save as" command does not complete

Categories

(Core Graveyard :: File Handling, defect)

PowerPC
Mac System 8.6
defect
Not set
major

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 143543

People

(Reporter: scrmntomts, Assigned: law)

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:1.0.0) Gecko/20020529 BuildID: 2002052917 It just won't save web pages - the command does not complete Reproducible: Always Steps to Reproduce: 1.Choose "Save page as" from file menu 2.The hard disk accesses momentarily (disk light flashes) 3."Save page as" dialog box never comes up Actual Results: Nothing Expected Results: "Save page as" dialog box appears, with options for saving
So OS 8.6 (branch and trunk) is completely useless because the saving dialog doesn't let you save.
Assignee: Matti → law
Component: Browser-General → File Handling
QA Contact: imajes-qa → sairuh
I get a similar result under Linux Mozilla/5.0 (build id: 2002052918) When I have a PDF file loaded under Acrobat ver 4.0 and I choose "Save Page as" from the "File" menu, nothing happens. I was able to save one file by letting it sit in the browser overnight, but this is not a very practical solution. :-) (In this overnight case the dialog box appeared as expected and I was able to save the file.) In contrast, when I used Netscape 6.2.1 (for Linux) and chose "Save as", I get a dialog box that lets me proceed with saving the file.
WorksForMe using Mac/2002072203/9.2.2. scrmntomts@aol.com, is this problem still reproducible using a current build? If so, can you reproduce this problem using a new Mozilla user profile? (Bob Dingman, that's potentitally a different enough problem to warrant your filing a separate bug about it.)
Severity: blocker → major
QA Contact: sairuh → petersen
Probably a dup. *** This bug has been marked as a duplicate of 143543 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.