Closed Bug 301359 Opened 19 years ago Closed 17 years ago

Two tabs with focus rect, at the same time

Categories

(Firefox :: Tabbed Browser, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: eru, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b3) Gecko/20050712 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b3) Gecko/20050712 Firefox/1.0+

If you select a FF tab so that a focus rect is shown on it an then open a new
tab by right-clicking on a bookmark menu item then you can end up having two
tabs which display a focus rect, at the same time
It happens with both FF 1.0.5 and DeerPark alpha2

Reproducible: Always

Steps to Reproduce:
1.Open FF with a tab displayed (blank or with a custom Home Page)
2.Right click on a bookmark from the Bookmarks menu
3.Left click on the new tab

Actual Results:  
Both tabs have a focus rect on them

Expected Results:  
Just one (the second, I suppose) tab shows the focus rect
I was wrong, it just happens with DeerPark. I tried to launch FF while having DP
running and I just got another instance of DP.
I forgot to say: in step 1 you obviously have to left click the first tab to
give focus to it.
Opened a Deerpark Alpha 2 with a new profile, opened 3 tabs, focussed one of
them, rightclicked and opened a bookmarks toolbar item in a new tab, and the
result: no focussed tabs at all :)
May be related: Bug 297421.
The whole focus system of Deerpark Alpha 2 is quite "strange", another example
is: open a tab and give it focus, open a second tab (none of them as a focus
rect), then go back to the first: it displays the focus rect but cursor keys do
not work.
Matteo, have you seen this on the current versions of Firefox?

If not, please close this bug as WORKSFORME. Thanks.
Whiteboard: CLOSEME 08/21
Tested FF 2.0.0.5 on both linux and winxp, works fine.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
Whiteboard: CLOSEME 08/21
You need to log in before you can comment on or make changes to this bug.