Closed Bug 416612 Opened 17 years ago Closed 17 years ago

Downloading causing numerous errors in the Error Console

Categories

(Toolkit :: Downloads API, defect)

x86
Windows Vista
defect
Not set
major

Tracking

()

RESOLVED INVALID

People

(Reporter: jmjjeffery, Unassigned)

Details

(Keywords: regression)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9b4pre) Gecko/2008020912 Minefield/3.0b4pre Firefox/3.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9b4pre) Gecko/2008020912 Minefield/3.0b4pre Firefox/3.0 Downloading files, I used for test: http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/FX-WIN32-TBOX-trunk/ Opening the error console2 I see: Error: gDownloadMgr is not defined Source file: chrome://browser/content/browser.js Line: 6980 Numerous entries during the download. The download info is showing in the Status bar - but there is no progress meter showing. Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: Errors in the Console2 Expected Results: No errors. Vista HP Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9b4pre) Gecko/2008020912 Minefield/3.0b4pre Firefox/3.0 ID:2008020912 < Recent Hourly build.
Keywords: regression
Version: unspecified → Trunk
Further testing in Safe-mode, and a New Profile.. I don't see the errors as noted above. However, I have other extensions that use the Statusbar. Statusbar clock and ForecastFox - so maybe its a 'positional' issue if other items are on the Statusbar ? I still see no 'progress meter' but the download status shows. I also made sure I had the js strict errors enabled in about:config since Console2 forces those by default.
More... Now I can't repo this with my working Profile. I'll leave it open till someone can look at the previous errors.
I'm going to close this INVALID, I've not been able to reproduce the error through several different hourly's & nightlys.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.