If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

nsIDownloadManager.open(..) no longer supported in Mozilla 1.9

RESOLVED FIXED

Status

Developer Documentation
General
RESOLVED FIXED
10 years ago
5 years ago

People

(Reporter: Victor Gubin, Unassigned)

Tracking

Details

(Reporter)

Description

10 years ago
User-Agent:       Opera/9.25 (Windows NT 5.1; U; ru)
Build Identifier: 

nsIDownloadManeger.open(..) no longer supported but documentation include it.
The special interface  nsIDownloadManagerUI now utillized.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.
(Reporter)

Comment 1

10 years ago
Sorry link http://developer.mozilla.org/en/docs/nsIDownloadManager
Assignee: basil → nobody
Component: PRD Change Request → Download Manager
Product: Documentation → Firefox
QA Contact: prd.change → download.manager
Version: unspecified → Trunk

Updated

10 years ago
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: dev-doc-needed
Summary: nsIDownloadManeger.open(..) no longer supported in Mozilla 1.9 engine → nsIDownloadManager.open(..) no longer supported in Mozilla 1.9 engine
This is just a documentation bug, right?
Component: Download Manager → Documentation Requests
Keywords: dev-doc-needed
Product: Firefox → Mozilla Developer Center
QA Contact: download.manager → doc-request
Summary: nsIDownloadManager.open(..) no longer supported in Mozilla 1.9 engine → nsIDownloadManager.open(..) no longer supported in Mozilla 1.9
Version: Trunk → unspecified

Comment 3

10 years ago
Just fixed, yes was just a doc bug.

http://developer.mozilla.org/en/docs/index.php?title=nsIDownloadManager&diff=next&oldid=66560
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
(Assignee)

Updated

5 years ago
Component: Documentation Requests → Documentation
Product: Mozilla Developer Network → Mozilla Developer Network
Component: Documentation → General
Product: Mozilla Developer Network → Developer Documentation
You need to log in before you can comment on or make changes to this bug.