[BETA]Move Install.fileXxx methods onto their own object

VERIFIED FIXED in M13

Status

Core Graveyard
Installer: XPInstall Engine
P3
critical
VERIFIED FIXED
19 years ago
3 years ago

People

(Reporter: dveditz, Assigned: dbragg)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

19 years ago
We should create a global File object in the install context to contain the
the current fileXxxx and dirXxxx methods from Install.  These still have to
know about the global "Install" object so actions can be queued, but the
namespace will be cleaner and easier to document.
(Reporter)

Updated

19 years ago
Target Milestone: M11
(Reporter)

Updated

19 years ago
Severity: normal → critical
Target Milestone: M11 → M12

Updated

19 years ago
Blocks: 18951
(Reporter)

Updated

19 years ago
Summary: Move Install.fileXxx methods onto their own object → [BETA]Move Install.fileXxx methods onto their own object
Target Milestone: M12 → M13

Comment 1

19 years ago
Bulk move of XPInstall (component to be deleted) bugs to Installer: XPInstall
Engine
(Assignee)

Updated

19 years ago
Assignee: dveditz → dbragg
Status: ASSIGNED → NEW
(Assignee)

Comment 2

19 years ago
dveditz reassigning to dbragg
(Assignee)

Updated

19 years ago
Status: NEW → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
(Assignee)

Comment 3

19 years ago
fixed.  Now you can reference these methods from FileOp.<whatever> as well as
the Install.<whatever> format.

Comment 4

19 years ago
Reassigning QA Contact to David.
QA Contact: jimmylee → depstein

Comment 5

19 years ago
tested each Fileop method. Each one is supported in the "File" object, although 
there are several problems (submitted bugs for these).
Status: RESOLVED → VERIFIED

Updated

18 years ago
No longer blocks: 18951
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.