Closed Bug 308420 Opened 19 years ago Closed 19 years ago

blue highlighting of profile names in Profile Manager is randomly unavailable

Categories

(Toolkit :: Startup and Profile System, defect)

x86
Windows XP
defect
Not set
trivial

Tracking

()

VERIFIED DUPLICATE of bug 279497

People

(Reporter: alimadzi, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050913 (No IDN) Firefox/1.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050913 (No IDN) Firefox/1.4

I have Profile Manager set to open automatically on launch.  I have two profiles
that I switch between.  I noticed that sometimes the most recently used profile
is highlighted by default and clicking on the other one highlights it.  However,
at other times, neither profile is highlighted on launch and only the first
profile can be highlighted by clicking on it (although the other one can be
selected and used without the visual cue of highlighting).  Double clicking on a
name still works in all cases.

Reproducible: Sometimes

Steps to Reproduce:
1. Set up two profiles.
2. Launch Firefox and click on each profile name.
3. Repeat.

Actual Results:  
Blue highlight not present on startup.  Unable to highlight second profile by
clicking on it.

Expected Results:  
Most recently used profile should always be highlighted on startup.  All other
profiles should highlight when clicked on.

These are upgraded 1.0.6 profiles.  I'm not sure if that is relevant or not.
Status: UNCONFIRMED → NEW
Ever confirmed: true

*** This bug has been marked as a duplicate of 279497 ***
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Sorry.  I really tried to make sure it wasn't a dupe, but I guess I wasn't quite
thorough enough.  Searched for "profile manager" and read the titles of all 57
results.  Nothing seemed to match.  I'll be more careful in the future.  Last
thing I want to do is waste someone's time.
Status: RESOLVED → VERIFIED
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.