Closed Bug 23260 Opened 25 years ago Closed 13 years ago

Ability to see which profile currently in use

Categories

(SeaMonkey :: Startup & Profiles, enhancement, P3)

Product:
SeaMonkey
Component:
Startup & Profiles
Type:
enhancement

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 670561
Milestone:
Future

People

(Reporter: bugzilla, Unassigned)

References

Details

(Whiteboard: [this is not INVALID but it might be WONTFIX])

After you start Mozilla it's impossible to see which profile it was started with. There should be a small text in the pref stating which profile mozilla was started with. Just something like: "Current Profile: gemal"
Target Milestone: M14
Bulk move of all Pref UI component bugs to new Preferences component. Pref UI component will be deleted.
Component: Pref UI → Preferences
Would it work just to stick some text on the status bar? By the build id #?
profile stuff
Assignee: matt → ben
changing component and QA contact
Component: Preferences → Profile Manager FrontEnd
QA Contact: sairuh → gbush
I'd do this sort of like how 4.x does it, with a few more enhancements. e.g. Preferences for Ben Goodger Bookmarks for Ben Goodger etc. this requires 32885
Status: NEW → ASSIGNED
Depends on: 32885
not a priority, pushing out as far as possible.
Target Milestone: M14 → M20
Severity: normal → enhancement
Summary: Ability to see which profile currently in use → [RFE] Ability to see which profile currently in use
Move to "Future" milestone.
Target Milestone: M20 → Future
Profile Manager FE bugs --> me
Assignee: ben → blakeross
Status: ASSIGNED → NEW
-> UI Design, pass to Ben when done.
Assignee: blake → mpt
Component: Profile Manager FrontEnd → User Interface Design
QA Contact: gbush → zach
RFE cleanup. RFE is already indicated by the Severity field...Sorry for the spam!
Summary: [RFE] Ability to see which profile currently in use → Ability to see which profile currently in use
*** Bug 99226 has been marked as a duplicate of this bug. ***
Blocks: 60299
Keywords: mozilla1.1
Some of the information you want can be often found w/: about:config under "browser.cache.directory" or "mail.root.*"
Keywords: mozilla1.2
.
Assignee: mpt → ben
Component: User Interface Design → Profile Manager FrontEnd
QA Contact: zach → ktrina
side note: in recent trunk builds, the Bookmark Mgr window now displays the profile name in the titlebar.
No longer blocks: 60299
No longer depends on: 32885
Keywords: mozilla1.1, mozilla1.2
OS: Windows 98 → All
Hardware: PC → All
*** Bug 196445 has been marked as a duplicate of this bug. ***
May be the existing profile should be greyed out in the initial profile selection dialogue box
Current profile is not greyed out in profile manager dialog of Tools->Switch Profile. To grey that seems to be solution.
Product: Browser → Seamonkey
Assignee: bugs → nobody
QA Contact: ktrina → profile-manager
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
(In reply to comment #14) > side note: in recent trunk builds, the Bookmark Mgr window now displays the > profile name in the titlebar. This doesn't seem to be the case anymore with SeaMonkey 2.0b1pre. (In reply to comment #16) > May be the existing profile should be greyed out in the initial profile > selection dialogue box When you open the Profile Manager the currently used profile is not greyed out, but it is selected. Bug 223169 might be a better solution for this bug.
The backend is already there, since it's possible to display the current profile folder at any time by means of the Error Console, see http://kb.mozillazine.org/Profile_folder_-_SeaMonkey#Other_profile_locations — there is also the "Open Containing Foplder" button near the top of the new about:support page. There remains the question of designing the UI. I agree that it would be nice to be able to display the current profile (profile name, profile folder, or both?). I see the following alternatives: - add it to about:support - leave it for an extension (Nightly Tester Tools? MR-Tech Toolkit? both?) I'll confirm this RFE, I'll even vote for it, but I'm also adding to the CC some guys who have (I think) the power of WONTFIXing it, or who might otherwise have something interesting to say in the matter.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Whiteboard: [this is not INVALID but it might be WONTFIX]
(In reply to comment #26) > - add it to about:support Actually it already has a button to open the profile folder.
(In reply to comment #26) > - add it to about:support Either that, in which case I'd propose to move it to toolkit, or else this is WONTFIX.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.