Active tab is not visually delimited and tab delimiters appear only on mouseover

RESOLVED INCOMPLETE

Status

Thunderbird
Toolbars and Tabs
RESOLVED INCOMPLETE
6 years ago
2 years ago

People

(Reporter: Andrei Boros, Unassigned)

Tracking

24 Branch
x86_64
Windows 7

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(5 attachments)

(Reporter)

Description

6 years ago
Created attachment 656378 [details]
tb15-tabs.png

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:15.0) Gecko/20100101 Firefox/15.0
Build ID: 20120824154833

Steps to reproduce:

Just upgraded from TB 14 to TB 15 on 3 different computers. 


Actual results:

1) visually, the tabs no longer have any delimiter
2) active tab is not visually highlighted in any way 
3) tab delimiters are visible (new rounded corners style) but only when mouse cursor is over that tab, but not the active tab.
4) the tab for the window telling me about TB and that I just upgraded has no title, and without the delimiters, I can't even tell it exists
5) upgrading a TB14 to T15 that has no email accounts configured yet yields the first tab as an empty window with only "create account" button, but this tab has only a folder icon, no title, and is not delimited visually even when hovering mouse over it. 

In FF15 tabs are displayed and delimited properly, including active tab and mouse over.


Expected results:

1) tabs should be visually delimited
2) active tab should be visually highlighted.
I've just tried this on Windows XP using the classic windows theme, and using the default theme in Thunderbird - which I'm guessing is the set-up that you are using.

I see all the delimiters, and the tabs are highlighted/shown at the correct times.

Have you tried running in safe mode, maybe an extension or something is getting in the way?
Maybe it could also be a HW-accelleration problem. Please can you check if it is used (Help -> Troubleshooting Information. Then on bottom you see the information)? Can you post then this info? If enabled, could you go to Options -> Advanced -> General and then click on 'Config Editor...'. In the opening window accept the warning. In search field put gfx.direct2d.disabled. If this is on false double click the entry, it should change to true. Now restart TB.
(Reporter)

Comment 3

6 years ago
Ok, first I would like to highlight the fact that I encountered this on 3 different computers, with completely different hardware, where TB15 tabs have the issue and FF15 tabs work fine. 

computer #1
Adapter DescriptionATI Radeon 9550 / X1050 Series
WebGL RendererBlocked for your graphics driver version. Try updating your graphics driver to version 10.6 or newer.
GPU Accelerated Windows0/2. Blocked for your graphics driver version. Try updating your graphics driver to version 10.6 or newer.

(i use the original CD version of the drivers, I had system stability issues with newer graphics drivers downloaded from their site)

computer #2
Adapter DescriptionMobile Intel(R) 965 Express Chipset Family
Driver Version6.14.10.4906
WebGL RendererBlocked for your graphics driver version. Try updating your graphics driver to version 6.14.10.5218 or newer.
GPU Accelerated Windows0/1. Blocked for your graphics driver version. Try updating your graphics driver to version 6.14.10.5218 or newer.
gfx.direct2d.disabled = true (default)

(I have only limited administrative privileges on this system [work related])
(I am sure this is a common situation for many users, and also sysadmins caught up in update frenzy, really)
gfx.direct2d.disabled = true (default)

computer #3
AMD Radeon HD 6500 series
WebGL renderer : Google inc .--ANGLE OpenGL ES 2.0
GPU accelerated windows : 0/1
gfx.direct2d.disabled = true (default)

=============================================
a) restarting with add-ons disabled (via help menu) changes nothing. Same behaviour. (on all 3 computers)
b) gfx.direct2d.* are on their default values. I tried toggling them, and all 4 combination yield the same thing. The issue described. 
c) computer #3 has no accounts configured (yet) and no addons installed. It is a fresh installation with TB13 and when I wanted to configure the accounts, first I checked for updates and got TB15. 
d) interestingly enough gfx.direct2d.disabled on FF15 has default value "false" and default value "true" on TB15. 
e) I have the same "troubleshooting info" in FF15 (about webGL blocked) but tabs are displayed correctly and work visually correctly in FF15 (default theme)
(Reporter)

Comment 4

6 years ago
TB 15.0.1 exhibits same behaviour.
(Reporter)

Comment 5

6 years ago
Confirmed on 3 more computers running 2 different XP Pro kits (packaged by brand manufacturers, HP and IBM).
(Reporter)

Comment 6

6 years ago
Created attachment 670353 [details]
tab visual in TB16
(Reporter)

Comment 7

6 years ago
Just upgraded to TB16. 
There is a visual difference in this new version, however, still far from correct. 

The current tab is NOT highlighted by any visual cue.
The the inactive tabs next to the active tab, regardless of which one is active, is missing some of the visual cues.
The first tab (leftmost tab) has no visual cue on the left.
The last tab (rightmost tab) has no visual cue on the right.
Version: 15 → 16
(Reporter)

Updated

4 years ago
OS: Windows XP → Windows 7
Hardware: x86 → x86_64
Version: 16 → 24
(Reporter)

Comment 8

4 years ago
Created attachment 8377005 [details]
tb-tabs-w7.png

This screenshot was taken on Windows 7 x64 with windows classic theme and TB-24.3. 

It goes again to show that the visual delimiters for the tabs are wrong. 

- current tab not visually delimited (at all)
- Starting with the second tab to the right of the first one (which is active), a tiny vertical line is seen. This yields confusion. 
- mouse over shows a nice, curved, tab highlight, but this visual effect is done improperly, as on classical theme (which is the least resource consuming) these decorations simply overflow down onto the rest of the window. I know, a couple of pixels, but it is wrong. 

Using one of the pretty, shiny themes with colorful and alpha effects on the window decorations, the tabs look ok in TB. 
But never on the classic theme, for those who want their resources used for actual work rather then pretty packaging.
(Reporter)

Comment 9

4 years ago
I have changed the flags to indicate win7x64, but the problem is the same on x86 and x64 and winxp and winvista and win7
I'm sorry but I can't reproduce this on XP nor on Win7.
(Reporter)

Comment 11

4 years ago
(In reply to Richard Marti (:Paenglab) from comment #10)
> I'm sorry but I can't reproduce this on XP nor on Win7.

Classic theme?
(Reporter)

Comment 12

4 years ago
Created attachment 8377247 [details]
tb-aero.png

(In reply to Richard Marti (:Paenglab) from comment #10)
This is the exact same machine and TB installation. 
The only thing that changed is that I changed to "Windows 7 Aero" theme.
Created attachment 8377248 [details]
Correct on W7 Classic

(In reply to Andrei Boros from comment #11)
> (In reply to Richard Marti (:Paenglab) from comment #10)
> > I'm sorry but I can't reproduce this on XP nor on Win7.
> 
> Classic theme?

Yep, for you drawintitlebar disabled.
(In reply to Andrei Boros from comment #12)
> Created attachment 8377247 [details]
> tb-aero.png
> 
> (In reply to Richard Marti (:Paenglab) from comment #10)
> This is the exact same machine and TB installation. 
> The only thing that changed is that I changed to "Windows 7 Aero" theme.

But the tab is to white and the main toolbar has a white area on the top.
Could you try the Earlybird from here: http://www.mozilla.org/en-US/thunderbird/channel/#aurora ? This has a different tab implementation more similar to Firefox Australis. Best would be if you would test with a new profile to be sure to not damage your working profile.

Comment 16

2 years ago
Andrei, 
Do you still see this with Thunderbird 38?
Flags: needinfo?(andrixnet)

Updated

2 years ago
Whiteboard: [closeme 2016-02-10]

Comment 17

2 years ago
Resolved per whiteboard
Status: UNCONFIRMED → RESOLVED
Last Resolved: 2 years ago
Flags: needinfo?(andrixnet)
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2016-02-10]
You need to log in before you can comment on or make changes to this bug.