516573 - Page title doesn't match active tab's title when using theme in personas

Status: RESOLVED DUPLICATE of bug 508134

(Mozilla Labs Graveyard :: Personas Plus, defect)

Description

[Gabriela [:gaby2300]]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; es-AR; rv:1.9.2a2pre) Gecko/20090910 Namoroka/3.6a2pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-AR; rv:1.9.2a2pre) Gecko/20090910 Namoroka/3.6a2pre

Whenever I hover my mouse on a theme within the personas site the new theme is displayed, the personas tab is active but it's not the tab you displayed. You can see this other tab and below and underneath you can see another tab. The only way to go back to the usual tab's behaviour is to activate the tab displayed (which isn't the active one) two or three times. As soon as you move your mouse to do this, the theme disappears. Only then you'll be able to see the actual active tab displayed.
Build: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-AR; rv:1.9.2a2pre) Gecko/20090910 Namoroka/3.6a2pre

Reproducible: Always

Steps to Reproduce:
1. Choose any personas theme and wear it
2. Open the personas site on a new tab.
3. Hover the mouse to a theme.
4. Move your mouse.

Actual Results:  
1. Choose any personas theme and wear it
2. Open the personas site on a new tab.
3. Hover the mouse to a theme.
4. The theme is displayed.
5. The active tab is not the displayed tab.


Expected Results:  
1. Choose any personas theme and wear it
2. Open the personas site on a new tab.
3. Hover the mouse to a theme.
4. The theme is displayed.
5. The active tab is the displayed tab.

Comment 1

[Gabriela [:gaby2300]]

Attachment: The new personas theme is diplayed, the personas tab is active but it's not the displayed one

Comment 2

[Myk Melez [:myk] [@mykmelez]]

This sounds like a duplicate of bug 508134, which has been fixed on the trunk but hasn't landed in Gecko 1.9.2 (the Firefox 3.6 development branch) yet.  I am marking it a duplicate, but please reopen the bug if I misunderstand or if the fix for that bug doesn't fix this one.