Closed Bug 194921 Opened 22 years ago Closed 22 years ago

Save Page As fails to save anything

Categories

(Core Graveyard :: File Handling, defect)

PowerPC
macOS
defect
Not set
blocker

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: tracy, Assigned: janv)

Details

(Keywords: smoketest)

seen on mac commercial and mozilla builds 2003-02-25-03-trunk

-Browse a web page
-select File | Save Page As
-use web complete...Save page

tested results: nothing is saved.

expected results:  the web page and an associated folder are saved.

note: this seems to be mac only...linux build 2003-02-25-08-trunk works fine. 
no windows build yet
Are you using download manager or progress dialog?
Save As dialog
any errors in the JS console?  Does using download manager work ok?
Using progress dialog for Save As is broken

workaround: Select open the download manager in preferences | Navogator
Downloads. This saves the page and associatd files as expected.

can this be a valid workaround, or is the "progress dialog" failure a blocker on
its own?



It's a blocker on its own, imo.  So to repeat, any errors in the JS console?  ;)

See also the checkin I made at 8:09am this morning; that was supposed to fix the
exact issue you're seeing...  I just noticed that the mac build you tested on is
from way before then; any chance of retesting with an 8am or later mac build?
Same problem with windows 2003022508

JS console:
Error: [Exception... "Component returned failure code: 0x80040154
(NS_ERROR_FACTORY_NOT_REGISTERED) [nsIDownload.init]"  nsresult: "0x80040154
(NS_ERROR_FACTORY_NOT_REGISTERED)"  location: "JS frame ::
chrome://communicator/content/contentAreaUtils.js :: foundHeaderInfo :: line
380"  data: no]
Source File: chrome://communicator/content/contentAreaUtils.js
Line: 380
Does that build have the 8:09 patch in it?  (unjar the relevant jar and check)
The patch in nsProgressDialog.js is not in this build, still seeing break
instead of return.
Ok.  Does switching it to return make the problem go away?  Or should I back out
the checkin for bug 91969?
Ok... I'm not sure how the tree opened with a pending smoketest blocker, but....
Is this still an issue with a Feb 26 build?
Flags: blocking1.3?
Flags: blocking1.3?
tracy, how does this work with today's mozilla bits?
works with todays mac mozilla build 2003-02-26-03-trunk (progress dialog
selected in prefs)
bill law not working on mozilla code.  Reassigning to samir to find a new owner
after talking with bill.
Assignee: law → sgehani
WFM 2003022610 Win2000
samir says -> varga
Assignee: sgehani → varga
So.... if no one is seeing this bug anymore, why is it still open?  As I said in
comment 5, I landed a fix for this yesterday; I just needed to verify that it
was indeed fixed.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
WFM, MacOS X, Build 2003022603
verified per comment #12
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.