Features/Thunderbird/Tabs On Top
Status
| Tabs on Top | |
| Stage | Complete |
| Status | Complete |
| Release target | Thunderbird 11 |
| Health | OK |
| Status note | ` |
{{#set:Feature name=Tabs on Top
|Feature stage=Complete |Feature status=Complete |Feature version=Thunderbird 11 |Feature health=OK |Feature status note=` }}
Team
| Product manager | Blake Winton |
| Directly Responsible Individual | Blake Winton |
| Lead engineer | Mike Conley |
| Security lead | ` |
| Privacy lead | ` |
| Localization lead | ` |
| Accessibility lead | ` |
| QA lead | ` |
| UX lead | Blake Winton |
| Product marketing lead | ` |
| Operations lead | ` |
| Additional members | ` |
{{#set:Feature product manager=Blake Winton
|Feature feature manager=Blake Winton |Feature lead engineer=Mike Conley |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=` |Feature ux lead=Blake Winton |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=` }}
Open issues/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?
Stage 1: Definition
1. 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.
2. Users & use cases
This change would affect all Thunderbird users.
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
3. Dependencies
`
4. Requirements
`
Non-goals
`
Stage 2: Design
5. Functional specification
`
6. User experience design
`
Stage 3: Planning
7. Implementation plan
`
8. Reviews
Security review
`
Privacy review
`
Localization review
`
Accessibility
`
Quality Assurance review
`
Operations review
`
Stage 4: Development
9. Implementation
`
Stage 5: Release
10. Landing criteria
` {{#set: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?
|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. |Feature users and use cases=This change would affect all Thunderbird users.
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 |Feature dependencies=` |Feature requirements=` |Feature non-goals=` |Feature functional spec=` |Feature ux design=` |Feature implementation plan=` |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=` |Feature landing criteria=` }}
Feature details
| Priority | P1 |
| Rank | 050 |
| Theme / Goal | ` |
| Roadmap | ` |
| Secondary roadmap | ` |
| Feature list | Thunderbird |
| Project | ` |
| Engineering team | Thunderbird |
{{#set:Feature priority=P1
|Feature rank=050 |Feature theme=` |Feature roadmap=` |Feature secondary roadmap=` |Feature list=Thunderbird |Feature project=` |Feature engineering team=Thunderbird }}
Team status notes
| status | notes | |
| Products | ` | ` |
| Engineering | ` | ` |
| Security | sec-review-unnecessary | ` |
| Privacy | ` | ` |
| Localization | ` | ` |
| Accessibility | ` | ` |
| Quality assurance | ` | ` |
| User experience | ` | ` |
| Product marketing | ` | ` |
| Operations | ` | ` |
{{#set:Feature products status=`
|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=sec-review-unnecessary |Feature security health=OK |Feature security notes=` |Feature privacy status=` |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=` |Feature qa notes=` |Feature ux status=` |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}