Open
Bug 941009
Opened 11 years ago
Updated 1 year ago
[meta] Move Places integration from DownloadIntegration to DownloadHistory.jsm
Categories
(Toolkit :: Downloads API, task, P3)
Toolkit
Downloads API
Tracking
()
NEW
People
(Reporter: Paolo, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: meta)
The portions of the DownloadIntegration module that interact with Places should be moved to a separate Desktop-specific module, integrated using the system from bug 899013.
Comment 1•11 years ago
|
||
nsIDownloadHistory had been created for the purposes of integrating downloads with any underlying history implementation
Reporter | ||
Comment 2•11 years ago
|
||
The purpose here is to separate the code that is unused in products other than Desktop, including history observers, for which #ifdefs have been introduced now in B2G. This could be more likely a Desktop-specific module containing some Places integration code, rather than a Places-specific module, though we'll see what works best when we get there.
Reporter | ||
Comment 3•7 years ago
|
||
The new DownloadHistory.jsm module can be the main interface for all the interactions between Download objects and history. It depends on Places and provides Downloads API views on the data.
I don't know if going forward the nsIDownloadHistory interface should still exist separately. Even if DownloadHistory.jsm could end up depending on how the actual data is stored in Places, another level of indirection is probably unneeded.
Updated•6 years ago
|
Type: defect → task
Updated•6 years ago
|
Summary: Move Places integration from DownloadIntegration to DownloadHistory.jsm → [meta] Move Places integration from DownloadIntegration to DownloadHistory.jsm
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•