Fennec/Features/multitouch
Status
| Touch Events part 2: Multitouch | |
| Stage | Development |
| Status | In progress |
| Release target | Firefox 10 |
| Health | OK |
| Status note | Patches in progress. |
{{#set:Feature name=Touch Events part 2: Multitouch
|Feature stage=Development |Feature status=In progress |Feature version=Firefox 10 |Feature health=OK |Feature status note=Patches in progress. }}
Team
| Product manager | Thomas Arend |
| Directly Responsible Individual | Matt Brubeck (mbrubeck) |
| Lead engineer | Wes Johnston (wesj) |
| Security lead | ` |
| Privacy lead | ` |
| Localization lead | ` |
| Accessibility lead | ` |
| QA lead | Cami Urian [Cami irc] |
| UX lead | ` |
| Product marketing lead | ` |
| Operations lead | ` |
| Additional members | ` |
{{#set:Feature product manager=Thomas Arend
|Feature feature manager=Matt Brubeck (mbrubeck) |Feature lead engineer=Wes Johnston (wesj) |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=Cami Urian [Cami irc] |Feature ux lead=` |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=` }}
Open issues/risks
`
Stage 1: Definition
1. Feature overview
Touch Events part 1 exposed single-touch events to web content.
Touch Events part 2 will extend that to expose multi-touch events to Fennec chrome and web content. This will allow authors to build web pages that interact with multiple touch points at once. It will also be useful in Fennec chrome for implementing multi-touch gestures in JavaScript.
2. Users & use cases
- Expose multi-touch events (multiple simultaneous touch events) to content in Fennec.
- Compatibility with existing web content.
- Conformance with the W3C Touch Events editor's draft, including new attributes like radius/force/angle where available.
- Compatibility with a common subset of Safari/Opera functionality.
- Use touch events to implement gestures in Fennec chrome JavaScript.
3. Dependencies
`
4. Requirements
- No visible performance regressions.
- UI gestures (e.g. pinch zoom) still work unless pages deliberately prevent them.
Non-goals
- 100% compatibility with Safari or other browsers.
- Enable W3C touch events in desktop Firefox (will be done in future versions).
- Defining new gestures - will be done separately in Fennec/Features/gestures.
- Exposing gesture events to web content.
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
- bug 603008 - Support multi-touch on Android
- bug 544614 - Tracking bug for touch events in Fennec
Stage 5: Release
10. Landing criteria
` {{#set:Feature open issues and risks=` |Feature overview=Touch Events part 1 exposed single-touch events to web content.
Touch Events part 2 will extend that to expose multi-touch events to Fennec chrome and web content. This will allow authors to build web pages that interact with multiple touch points at once. It will also be useful in Fennec chrome for implementing multi-touch gestures in JavaScript. |Feature users and use cases=* Expose multi-touch events (multiple simultaneous touch events) to content in Fennec.
- Compatibility with existing web content.
- Conformance with the W3C Touch Events editor's draft, including new attributes like radius/force/angle where available.
- Compatibility with a common subset of Safari/Opera functionality.
- Use touch events to implement gestures in Fennec chrome JavaScript.
|Feature dependencies=` |Feature requirements=* No visible performance regressions.
- UI gestures (e.g. pinch zoom) still work unless pages deliberately prevent them.
|Feature non-goals=* 100% compatibility with Safari or other browsers.
- Enable W3C touch events in desktop Firefox (will be done in future versions).
- Defining new gestures - will be done separately in Fennec/Features/gestures.
- Exposing gesture events to web content.
|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=* bug 603008 - Support multi-touch on Android
- bug 544614 - Tracking bug for touch events in Fennec
|Feature landing criteria=` }}
Feature details
| Priority | P1 |
| Rank | 999 |
| Theme / Goal | ` |
| Roadmap | Firefox Mobile |
| Secondary roadmap | ` |
| Feature list | Mobile |
| Project | ` |
| Engineering team | Mobile platform |
{{#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 platform }}
Team status notes
| status | notes | |
| Products | ` | ` |
| Engineering | ` | ` |
| Security | sec-review-needed | imelven |
| 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-needed |Feature security health=Assigned |Feature security notes=imelven |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=` }}