Features/Thunderbird/Tabs On Top: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 1: Line 1:
{{FeatureStatus
{{FeatureStatus
|Feature name=Tabs on Top
|Feature name=Tabs on Top
|Feature stage=Draft
|Feature stage=Feature Inbox
|Feature health=OK
|Feature health=OK
}}
}}
Line 8: Line 8:
|Feature open issues and risks=* How does this impact the quick filter bar toggle?  Where should this button be placed?
|Feature open issues and risks=* How does this impact the quick filter bar toggle?  Where should this button be placed?
* How does this impact add-ons that assume that the menubar will be available across all tabs?  Do such add-ons exist?
* How does this impact add-ons that assume that the menubar will be available across all tabs?  Do such add-ons exist?
|Feature overview=As part of our ongoing UX refresh in Thunderbird, we'd like the tabs to be placed above the main Thunderbird menubar.  This is similar to what has emerged in common browser UI over the past few years.
|Feature overview=As part of our ongoing UX refresh in Thunderbird, we'd like the tabs to be placed above the main Thunderbird menubar.  This is similar to what has emerged in common browser UI's over the past few years.


This should be toggle-able, so that users can move the tabs back below the menu bar, preserving the current Thunderbird UX.
This should be toggle-able, so that users can move the tabs back below the menu bar, preserving the current Thunderbird UX.
|Feature users and use cases=This change would affect all users of Thunderbird.
|Feature users and use cases=This change would affect all Thunderbird users.


We want to support both tabs above and below the menubar, and careful thought will need to go into how this could impact add-ons that rely on the menubar being visible across all tabs.
The justification for this change is a more flexible UX.  Since tabs are currently below the main menu bar, the main menu bar persists regardless of the type of tab currently being displayed.  Thus, even if we're viewing a content tab, we still have menu buttons visible that do not apply at all to content tabs.
 
Generally, we sidestep this issue by having hooks that disable certain menu buttons for certain tabs (for example, the Get Mail button is disabled while viewing the Add-ons Manager tab).
 
What we propose to do instead is to move the tabs above the menubar, so that each tab type can have it's own menubar.  This has a number of benefits:
 
1)  More space for tabs that do not require a menubar
2)  The menubar is guaranteed to be applicable to the current tab
}}
}}
{{FeatureInfo
{{FeatureInfo
Confirmed users, Bureaucrats and Sysops emeriti
1,009

edits