1023825 - unusable top row (24.6.0)

Status: RESOLVED WORKSFORME

(Thunderbird :: Toolbars and Tabs, defect)

Description

[Alexander]

Attachment: Снимок.JPG

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:30.0) Gecko/20100101 Firefox/30.0 (Beta/Release)
Build ID: 20140605174243

Steps to reproduce:

(24.6.0)
I am trying to close or activate tab by moving cursor to the top of the screen and the left to the tabs


Actual results:

There is some empty unusable row over the tabs so i must down the cursor from that row to tabs


Expected results:

There should not be any empty unusable row iver the tabs, like it is at firefox.

Comment 1

[Wayne Mery (:wsmwk)]

I don't see anything wrong with your screen shot. It looks like my vista system where I use nightly builds.  I see
  Tabs
  Mail toolbar 
which I believe is correct behavior. And, if Thunderbird is full screen and cursor is at edge of the screen over a tab (but not physically in a tab) then clicking there activates the tab.

Are you looking for the Thunderbird menu?

Comment 2

[Alexander]

But for some reason at my windows 7 x64 SP1 Ult.
if Thunderbird is full screen and cursor is at edge of the screen over a tab (but not physically in a tab) then clicking there DOES NOT activates the tab. And as you can see (i believe this is a good screen shot) there some empty line OVER the tabs, where clicking does not do anything with tabs.
I creates a new profile and i see there is a same problem with a new profile, so i think it's a bug..

Comment 3

[Wayne Mery (:wsmwk)]

Andreas, can you reproduce with win7?

> I creates a new profile and i see there is a same problem with a new
> profile, so i think it's a bug..

excellent! thanks for testing that

> But for some reason at my windows 7 x64 SP1 Ult.
> if Thunderbird is full screen and cursor is at edge of the screen over a tab
> (but not physically in a tab) then clicking there DOES NOT activates the
> tab. And as you can see (i believe this is a good screen shot) there some
> empty line OVER the tabs, where clicking does not do anything with tabs.

On my win7 SP1 professional I see the same amount of space at the top. But I can't reproduce.

Comment 4

[Alexander]

"I see the same amount of space at the top. But I can't reproduce."
You see the empty line ?
What you can't reproduce ? I didn't understand..

Comment 5

[Wayne Mery (:wsmwk)]

The *behavior* I see is correct despite the little space at the top, which does not look excessive to me.  Not what I would call a row

Comment 6

[Alexander]

The behavior is correct because there is some space (or whtever it's called), and if there wasn't space this will be better. The question is why is there this space ?
Maybe that's because of fullhd resolution ?

Comment 7

[Richard Marti (:Paenglab)]

The upcoming TB 31 will behave like you expect with in fullscreen showing a 1px gap but still hovering/activating the tab when you are at the top with the mouse.

Comment 8

[Richard Marti (:Paenglab)]

I'm resolving as WONTFIX as in about 6 weeks TB 31 comes out and it makes no sense to fix this in TB 24 short before the update to TB 31.

Comment 9

[Alexander]

First: Where did you download TB31 ? I see only 24.6.0 as a last TB!
secind: I discover why TB acts like i described. It is because of scaling in windows 7. It was 125%!

Comment 10

[Alexander]

Attachment: windows scaling option screenshot

Comment 11

[Alexander]

I've added a screnshot so you can understand what scaling i mean.
So firefox acts well with 125% scaling, but TB, as you can see, not.

Comment 12

[Wayne Mery (:wsmwk)]

Attachment: screen shot 125% win7

this is me at 125%, with and without menu.
nightly/daily development build used by triagers and developers.
works fine.

I would bet beta works fine.
version 30 beta (soon 31 beta) can be found at http://www.mozilla.org/en-US/thunderbird/channel/

Comment 13

[Wayne Mery (:wsmwk)]

(In reply to Richard Marti (:Paenglab) from comment #8)
> I'm resolving as WONTFIX as in about 6 weeks TB 31 comes out and it makes no
> sense to fix this in TB 24 short before the update to TB 31.

WFM is equally appropriate, as the issue doesn't exist in when using the most current code - which is development, and the ultimate benchmark for bugzilla status :)