Closed Bug 597049 Opened 14 years ago Closed 14 years ago

ProfileManager needs to work with absolute paths

Categories

(Testing Graveyard :: ProfileManager, defect)

Product:
Testing Graveyard
Component:
ProfileManager
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jgriffin, Unassigned)

References

Details

The API in the Profile Manager allows for specifying a custom path for new profiles, but our UI doesn't.  

The existing Profile Manager in Firefox allows a custom path, so we should too.
Depends on: 602375
I'm promoting this to blocker-1.0.  Many of the API's already work correctly with absolute profile paths, but the UI does not.  Some users will doubtlessly have profiles.ini that utilizes absolute paths, and we don't want to behave badly in those cases.
Summary: Need to allow user to specify path for new profiles → ProfileManager needs to work with absolute paths
Whiteboard: [blocker-1.0]
Depends on: 607731
Depends on: 607732
Custom profile paths now supported during new profile:
http://hg.mozilla.org/automation/profilemanager/rev/6755f429eae2

Still needs support during copy and unarchiving operations.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Whiteboard: [blocker-1.0]
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.