Closed Bug 370807 Opened 19 years ago Closed 18 years ago

When have blank home page double click in tab bar opens two new tabs and unfocused

Categories

(Firefox :: Tabbed Browser, defect)

2.0 Branch
x86
Windows XP
defect
Not set
minor

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: giorgos.katsikatsos, Unassigned)

Details

(Whiteboard: CLOSEME 08/26)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1 When have blank home page double click in tab bar opens two new tabs and unfocused. I noticed the bug when installed firefox 2.0 in 4 boxes. 3 out of 4 had the same behaviour, but I did't realized until I made my home page blank and tried to open new tab by double clicking the tab bar. I use "tabbroswer preferences 1.3.1.1" Reproducible: Always Steps to Reproduce: 1. Put blank home page on firefox 2. Restart 3. Double click tab bar to open new tab Actual Results: Open 2 new tabs instead of 1 and unfocused. Expected Results: Open 1 new focused tab
I can't reproduce this with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1 Please retest in Firefox's safe-mode (to exclude extension/theme problems). Also a new profile or a re-install in a new empty folder could help. http://kb.mozillazine.org/Safe_Mode_(Firefox) http://kb.mozillazine.org/Profile_Folder
I have this problem. Using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
reporter do you still see that problem with latest version and in Safe Mode? if not please resolve this report as WORKSFORME
Whiteboard: CLOSEME 08/26
Hi Sorry, it seems that I forgot to answer the previous reply. Well, in fact, in safe mode it works correctly, with the same profile.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
Version: unspecified → 2.0 Branch
Verified
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.