Fennec/Features/TabletUI
Status
| Tablet UI - Keyboards & Others | |
| Stage | Development |
| Status | In progress |
| Release target | Firefox 8 |
| Health | OK |
| Status note | Functional patches almost complete; need visual implementation; will probably be ready to land early in Firefox 8 cycle. |
{{#set:Feature name=Tablet UI - Keyboards & Others
|Feature stage=Development |Feature status=In progress |Feature version=Firefox 8 |Feature health=OK |Feature status note=Functional patches almost complete; need visual implementation; will probably be ready to land early in Firefox 8 cycle. }}
Team
| Product manager | Thomas Arend |
| Directly Responsible Individual | Mark Finkle |
| Lead engineer | Matt Brubeck (mbrubeck), Chris Lord (Cwiis) |
| Security lead | ` |
| Privacy lead | ` |
| Localization lead | ` |
| Accessibility lead | ` |
| QA lead | Tony Chung, Naoki Hirata |
| UX lead | Brian Dils, Madhava Enros |
| Product marketing lead | ` |
| Operations lead | ` |
| Additional members | ` |
{{#set:Feature product manager=Thomas Arend
|Feature feature manager=Mark Finkle |Feature lead engineer=Matt Brubeck (mbrubeck), Chris Lord (Cwiis) |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=Tony Chung, Naoki Hirata |Feature ux lead=Brian Dils, Madhava Enros |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=` }}
Open issues/risks
- Need final visual designs.
- Finish and land patches.
Stage 1: Definition
1. Feature overview
Optimizing Fennec for larger tablet devices, e.g. by adjusting UI elements, buttons, font size.
- Goals
- Improved user experience on tablets, especially 10-inch Android tablets.
- Fit in better with Android 3.0 (Honeycomb) UI.
2. Users & use cases
`
3. Dependencies
`
4. Requirements
`
Non-goals
- 100% perfect fidelity to Honeycomb widgets/conventions.
Stage 2: Design
5. Functional specification
`
6. User experience design
Note: These are all early design concepts, not yet final specs:
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
- bug 655762 - Tracking bug.
bug 645725(FIXED) - Don't require two taps to open non-fullscreen landscape keyboard (e.g. Xoom)bug 655740(FIXED) - Make the prefs pane tablet friendlybug 656373(FIXED) - Turn off Form Assistant zooming, panning and next/prev on tablets- bug 656329 (ASSIGNED) - Use a Honeycomb-style action bar on Android tablets
- bug 664149 (ASSIGNED) - Move the app menu to the action bar in tablet mode.
- bug 653075 (NEW) - Present domain in identity box as we do with desktop
Stage 5: Release
10. Landing criteria
` {{#set:Feature open issues and risks=* Need final visual designs.
- Finish and land patches.
|Feature overview=Optimizing Fennec for larger tablet devices, e.g. by adjusting UI elements, buttons, font size.
- Goals
- Improved user experience on tablets, especially 10-inch Android tablets.
- Fit in better with Android 3.0 (Honeycomb) UI.
|Feature users and use cases=` |Feature dependencies=` |Feature requirements=` |Feature non-goals=* 100% perfect fidelity to Honeycomb widgets/conventions. |Feature functional spec=` |Feature ux design=Note: These are all early design concepts, not yet final specs:
|Feature implementation plan=` |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=* Test Plan |Feature operations review=` |Feature implementation notes=* bug 655762 - Tracking bug.
bug 645725(FIXED) - Don't require two taps to open non-fullscreen landscape keyboard (e.g. Xoom)bug 655740(FIXED) - Make the prefs pane tablet friendlybug 656373(FIXED) - Turn off Form Assistant zooming, panning and next/prev on tablets- bug 656329 (ASSIGNED) - Use a Honeycomb-style action bar on Android tablets
- bug 664149 (ASSIGNED) - Move the app menu to the action bar in tablet mode.
- bug 653075 (NEW) - Present domain in identity box as we do with desktop
|Feature landing criteria=` }}
Feature details
| Priority | P1 |
| Rank | 999 |
| Theme / Goal | ` |
| Roadmap | Firefox Mobile |
| Secondary roadmap | ` |
| Feature list | Mobile |
| Project | ` |
| Engineering team | Mobile front-end |
{{#set:Feature priority=P1
|Feature rank=999 |Feature theme=` |Feature roadmap=Firefox Mobile |Feature secondary roadmap=` |Feature list=Mobile |Feature project=` |Feature engineering team=Mobile front-end }}
Team status notes
| status | notes | |
| Products | ` | ` |
| Engineering | ` | ` |
| Security | pass | ` |
| 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=pass |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=` }}