Closed Bug 270037 Opened 20 years ago Closed 20 years ago

downloadmanager window shows no downloads, only XML parsing error description

Categories

(Toolkit :: Downloads API, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: frank.fuerntrath, Assigned: bugs)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

in the downloadmanager window, the following information is displayed:
XML Parsing Error:undefined entity; Location:
chrome://downloadmgr/content/downloadsidebar.xul
line number 135, column 27: 
toolbarbutton label="&cmd.option.label;"

Reproducible: Always
Steps to Reproduce:
1.start mozilla
2.press download manager tab
3.
-> FF
Assignee: download-manager → bugs
Product: Browser → Firefox
QA Contact: bmo
Summary: downloadmanager windox shows no downloads, only xml parsing error description → downloadmanager window shows no downloads, only XML parsing error description
Confirming on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a6)
Gecko/20041224 Firefox/1.0+, but when I start a download I see in the JavaScript
console

Error: Component returned failure code: 0x80004002 (NS_NOINTERFACE)
[nsISupportsArray.QueryElementAt]
Source File: 
Line: 440

Is this a different bug?
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a6) Gecko/20041227
Firefox/1.0+ (zip/Firefox 0.9 milestone profile)

WFM
hmm removing the FF program folder and installing again fixed it. Probably
overwriting dlls by the installer didn't work well. So WFM now.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a6) Gecko/20050101
Firefox/1.0+
The original report itself is invalid. downloadsidebar.xul is not a Firefox
file, it is part of an extension. If the extension doesn't work it's not an
issue with Firefox.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.