Closed Bug 43089 Opened 25 years ago Closed 25 years ago

nsChromeRegistry::GetProfileRoot uses filelocator!

Categories

(Core :: XUL, defect, P3)

All
AIX
defect

Tracking

()

RESOLVED FIXED
mozilla0.8

People

(Reporter: dougt, Assigned: ccarlen)

Details

Instead of using the filelocator, you should use the nsDirectoryService. The reason for this is that the filelocator requires the appshell crap whereas the directoryservice is built into xpcom. nsChromeRegistry::GetProfileRoot(nsCString& aFileURL) { nsCOMPtr<nsIFileLocator> fl; nsresult rv = nsComponentManager::CreateInstance("component://netscape/filelocator", nsnull, NS_GET_IID(nsIFileLocator), getter_AddRefs(fl));
Status: NEW → ASSIGNED
Target Milestone: --- → Future
-> nsbeta2. moving to m16. we're hammering out dependency issues and this is low hanging fruit.
Target Milestone: Future → M16
Then reassign it to someone else. I don't have time in M16 to deal with this issue.
-> jud
Assignee: hyatt → valeski
Status: ASSIGNED → NEW
M16 has been out for a while now, these bugs target milestones need to be updated.
m17 is out now, please update target
over to conrad.
Assignee: valeski → ccarlen
Target Milestone: M16 → mozilla0.8
Component: XP Miscellany → XP Toolkit/Widgets: XUL
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: brendan → xptoolkit.widgets
You need to log in before you can comment on or make changes to this bug.