152549 - Profile Manager UI needs to clearly indicate complete path.

Status: RESOLVED EXPIRED

(SeaMonkey :: Startup & Profiles, defect)

Description

[Jason Bassford]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1a) Gecko/20020617
BuildID:    2002061707

This is an attempt to salvage something out of bug 147421.

The profile manager UI needs to more clearly state exactly what it's going to
do.  When creating a profile, it should show the path that it's going to end up
creating.  Currently, it does not do this.  It shows "partial_path".  But it
then ends up creating "partial_path\profile_name\salted_directory".  The UI
should be more explicit, and should show the full path that will actually be
used in the UI.

Whether or not the profile_name or the salted_directory sub-folders get created
will be left for a separate bug.  But whatever path is actually created in the
end should be shown in the UI.  Not only does this let the person know what's
going on, but it also conveys to them the exact location of their personal
preferences, bookmarks, etc.

Reproducible: Always
Steps to Reproduce:
1. Create a new profile.

Actual Results:  The UI doesn't indicate exactly what it's going to be doing.

Expected Results:  There should be better feedback to the user about what's
going to happen.

Comment 1

[Jason Bassford]

Original summary: Profile Manager UI needs re-wording / clarity.
Changed summary: clearly indicate the partial profile path for new profile

Fixing wording change.  Need to be able to search in Bugzilla on "profile
manager" and "UI".  Also, this bug is not about indicating a *partial* profile
path - it currently *only* does so which is why I'm complaining - but about how
the UI should show the *full* path.

Comment 2

[Felix Miata]

Attachment: screenshot

I'm not sure I understand the behavior described in this bug. Does the
truncated pathname in this screenshot describe the behavior here? I didn't find
any other bugs that seem to apply. Screenshot is from 2003052113 OS/2 trunk at
120 DPI, but the same thing happens in W32 2003052508 trunk. I've been seeing
this for many moons.

Comment 3

[José Jeria]

Bug 200439 is the same as this one, but that one has 13 bugs to it already, how
about duping this one to that one for that reason?

Comment 4

[Robert Kaiser]

MASS-CHANGE:
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

Comment 5

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420