Closed Bug 1851332 Opened 10 months ago Closed 10 months ago

supernova: Allow to menu bar to top of page

Categories

(Thunderbird :: Untriaged, enhancement)

Thunderbird 115
enhancement

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1822991

People

(Reporter: eberger, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/117.0

Steps to reproduce:

opened supernova

Actual results:

apparently you can do a lot of customizing on the toolbar but cannot move the menu bar to the top of the page. That is where it has been forever and where I would like it to be in Supernova.

Expected results:

allow the user to put either the toolbar or menu bar at top of screen

Summary: supernova menu bar → supernova: Allow to menu bar to top of page

(In reply to eberger from comment #0)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/117.0

Steps to reproduce:

opened supernova

Actual results:

apparently you can do a lot of customizing on the toolbar but cannot move the menu bar to the top of the page. That is where it has been forever and where I would like it to be in Supernova.

Expected results:

allow the user to put either the toolbar or menu bar at top of screen

Hi eberger
This is something being asked several times in the Thunderbird Support Forum.
Currently you need to use 'userChrome.css' to fix this.
See an example as chosen solution here: https://support.mozilla.org/en-US/questions/1422908

This is covered in bug 1822991

Status: UNCONFIRMED → RESOLVED
Closed: 10 months ago
Duplicate of bug: 1822991
Resolution: --- → DUPLICATE

Thank you. Once I make this fix will I need to undo it when Supernova is updated to allow this setting through choices with standard menus?

I think the only potential change will be if the developers decide to incorporate the current Menu Bar within the 'Unified' toolbar.
I have met a lot of resistance to allowing the user to have the option of choosing where toolbars are located.
But, yes, if there are changes then it will not be necessary to use the 'userchrome.css' file. The easy fix would be to rename it as 'XuserChrome.css' then it is always available to rewrite etc should you need it.

Thank you. I've listened to the Supernova podcasts and it is all about matching the old user experience according to what they said, so it is surprising that there is resistance to allow users to achieve that.

You need to log in before you can comment on or make changes to this bug.