Firefox/Features/Panorama All Windows UI
Status
| All-Windows UI for Panorama | |
| Stage | Design |
| Status | ` |
| Release target | ` |
| Health | OK |
| Status note | ` |
{{#set:Feature name=All-Windows UI for Panorama
|Feature stage=Design |Feature status=` |Feature version=` |Feature health=OK |Feature status note=` }}
Team
| Product manager | Asa Dotzler |
| Directly Responsible Individual | Alex Limi |
| Lead engineer | Tim Taubert |
| Security lead | ` |
| Privacy lead | ` |
| Localization lead | ` |
| Accessibility lead | ` |
| QA lead | ` |
| UX lead | Alex Limi |
| Product marketing lead | ` |
| Operations lead | ` |
| Additional members | ` |
{{#set:Feature product manager=Asa Dotzler
|Feature feature manager=Alex Limi |Feature lead engineer=Tim Taubert |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=` |Feature ux lead=Alex Limi |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=` }}
Open issues/risks
`
Stage 1: Definition
1. Feature overview
After the global storage for Panorama is ready we need to implement the user interface to handle all tabs and tab groups from all windows.
This feature falls primarily in the Discover category (from the "Discover, Experience, and Connect" vision statement.)
2. Users & use cases
- Panorama shows tabs and tab groups from all windows
- all panorama views show the same in every window
- spatial layout is constant when switching between multiple windows with different sizes and aspects
3. Dependencies
`
4. Requirements
- Panorama screen should have the same content, no matter which window you open it in
- A new window is a new Panorama group (unless the first thing you do in that window is to go to a group, in which case it drops the empty group)
- You should be able to swap the contents of two windows by entering both windows and selecting the other group
- The goal is to have a spatially useful appearance in different-sized windows (and on different-sized monitors), so we might have to store the group position and size as a percentage/ratio of the window, since pixel positioning isn't going to work.
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
Provide test coverage for the new UI. There are lots of existing tests that will have to be re-written or adapted to the new behavior.
Operations review
`
Stage 4: Development
9. Implementation
Stage 5: Release
10. Landing criteria
` {{#set:Feature open issues and risks=` |Feature overview=After the global storage for Panorama is ready we need to implement the user interface to handle all tabs and tab groups from all windows.
This feature falls primarily in the Discover category (from the "Discover, Experience, and Connect" vision statement.) |Feature users and use cases=* Panorama shows tabs and tab groups from all windows
- all panorama views show the same in every window
- spatial layout is constant when switching between multiple windows with different sizes and aspects
|Feature dependencies=` |Feature requirements=* Panorama screen should have the same content, no matter which window you open it in
- A new window is a new Panorama group (unless the first thing you do in that window is to go to a group, in which case it drops the empty group)
- You should be able to swap the contents of two windows by entering both windows and selecting the other group
- The goal is to have a spatially useful appearance in different-sized windows (and on different-sized monitors), so we might have to store the group position and size as a percentage/ratio of the window, since pixel positioning isn't going to work.
|Feature non-goals=` |Feature functional spec=* Technical Design |Feature ux design=` |Feature implementation plan=` |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=Provide test coverage for the new UI. There are lots of existing tests that will have to be re-written or adapted to the new behavior. |Feature operations review=` |Feature implementation notes=* bug 578512 |Feature landing criteria=` }}
Feature details
| Priority | P3 |
| Rank | 999 |
| Theme / Goal | Discover |
| Roadmap | Firefox Desktop |
| Secondary roadmap | ` |
| Feature list | Desktop |
| Project | ` |
| Engineering team | Desktop front-end |
{{#set:Feature priority=P3
|Feature rank=999 |Feature theme=Discover |Feature roadmap=Firefox Desktop |Feature secondary roadmap=` |Feature list=Desktop |Feature project=` |Feature engineering team=Desktop front-end }}
Team status notes
| status | notes | |
| Products | ` | ` |
| Engineering | ` | ` |
| Security | ` | ` |
| 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=` |Feature security health=` |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=` }}