Closed
Bug 656718
Opened 14 years ago
Closed 14 years ago
Duplicate dock icon upon restarting if pinned to dock
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: steve.g.kelly, Unassigned)
Details
(Whiteboard: [bugday-20110513])
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0.1) Gecko/20100101 Firefox/4.0.1
Build Identifier: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0.1) Gecko/20100101 Firefox/4.0.1
Upon updating an add-on in Firefox, occasionally a duplicate Firefox dock icon will appear when it restarts and run from that icon rather than the pinned dock icon
This happens (note the duplicate firefox icon at the bottom):
http://i.imgur.com/N07ya.png
Reproducible: Couldn't Reproduce
Steps to Reproduce:
1. Update an add-on or Firefox itself
2. Restart Firefox
(only happens occasionally)
Actual Results:
Again, it only happens occasionally. Doesn't happen after a normal non-update restart.
Expected Results:
Run FF from the pinned dock icon rather than create a new one and run from that.
Comment 1•14 years ago
|
||
Unable to replicate in Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:5.0a2) Gecko/20110513 Firefox/5.0a2
Can you try to replicate this in the latest nightly of Aurora available from http://www.mozilla.com/en-GB/firefox/channel/
Are there are specific add-ons that you have seen this behaviour with?
Whiteboard: [bugday-20110513]
Updated•14 years ago
|
Version: unspecified → 4.0 Branch
WFM on Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0a1) Gecko/20110522 Firefox/6.0a1
Also, could you see if the issue occurs if using Firefox in safe mode:
http://support.mozilla.com/kb/Safe+Mode
How about with a new, empty testing profile? (Don't install any addons into it)
http://support.mozilla.com/kb/Basic+Troubleshooting#w_8-make-a-new-profile
Setting resolution to Resolved WFM. Reporter, if you have anything new to add, please feel free to reopen this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•