User-Agent: Mozilla/5.0 (X11; U; Linux i686; fr; rv:188.8.131.52) Gecko/20091109 Ubuntu/9.10 (karmic) Firefox/3.5
This is clearly a regression from thunderbird 2...
in TB 3, if you use vertical mode... half of the new "message toolbar" (reply, forward, delete) is hidden, the From field is totally hidden...
I think this mode should be rethinked...
Many people on our firm use vertical view in TB2... i can't say : "with TB3 this mode would be worst than before..."
Steps to Reproduce:
1. Hava a 4/3 screen resolution 1280x1024
2. Switch on vertical mode
3. Click on message
half of the new "message toolbar" (reply, forward, delete) is hidden, the From field is totally hidden...
We should see at least the "from" field and the toolbar should be usable
Created attachment 414460 [details]
Screenshot showing the problem
The same problem exists in windows...
A workaround would be to customize it with CustomizeHeaderToolbar https://addons.mozilla.org/fr/thunderbird/addon/45601 and add the needed buttons to the main toolbar.
I came to report the same thing
(In reply to comment #3)
> A workaround would be to customize it with CustomizeHeaderToolbar
> https://addons.mozilla.org/fr/thunderbird/addon/45601 and add the needed
> buttons to the main toolbar.
The problem isn't missing buttons but that the buttons are covering the header fields. However using this extension you can set the buttons to "Icon" only mode which shrinks them a lot.
Still, I think the buttons should maybe appear above the header information, though this has the disadvantage of increasing the vertical size of the header bar (it already seems pretty large when using the "Classic" layout)
I can confirm this for the popular "tablet PCs" like the 1825PT(Z) or the T101MT. Working around this with added buttons to the top menu bar works. But this really needs to be worked out. Maybe TB can switch to another window layout automatically depending on the screen format/rotation. (Then it would be quite similar to what the new apple product does...possible? patent wise?)
Fixed by bug 519956 and bug 530047?
Marking fixed based on comment 6; if you still see the issue, feel free to reopen.