Fennec/Features/touch

From MozillaWiki
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
Please use "Edit with form" above to edit this page.

Status

Touch Events part 1: single-touch
Stage Shipped
Status `
Release target Firefox 6
Health OK
Status note `

{{#set:Feature name=Touch Events part 1: single-touch

|Feature stage=Shipped |Feature status=` |Feature version=Firefox 6 |Feature health=OK |Feature status note=` }}

Team

Product manager Thomas Arend
Directly Responsible Individual Matt Brubeck
Lead engineer Wes Johnson, Olli Pettay, Matt Brubeck
Security lead `
Privacy lead `
Localization lead `
Accessibility lead `
QA lead Martijn Wargers
UX lead `
Product marketing lead `
Operations lead `
Additional members `

{{#set:Feature product manager=Thomas Arend

|Feature feature manager=Matt Brubeck |Feature lead engineer=Wes Johnson, Olli Pettay, Matt Brubeck |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=Martijn Wargers |Feature ux lead=` |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=` }}

Open issues/risks

  • bug 653009 - Make preventDefault for touch events compatible with WebKit/Opera

Stage 1: Definition

1. Feature overview

Expose touch events to content for better interaction with web pages and services, and compatibility with WebKit/Opera and existing web content.

2. Users & use cases

  • Expose single-touch events to content in Fennec.
  • Don't let pages completely block navigation or sidebar panning.
  • Compatibility with existing pages like Google Maps.
  • Conformance with a subset of W3C Touch Events editor's draft.
  • Compatibility with a common subset of Safari/Android/WebKit functionality.

3. Dependencies

`

4. Requirements

  • No performance regressions on non-touch-event pages.
  • Acceptable performance of touch events in content. (Need more precise criteria?)
  • Sidebar (or some alternate form of navigation) is still accessible on pages that use touch events.

Non-goals

  • Expose multiple simultaneous touches to content (will be done in a part 2).
  • 100% conformance with W3C Touch Events spec (will be completed in future versions).
  • 100% compatibility with Safari or other browsers.
  • Enable W3C touch events in desktop Firefox (will be done in future versions).

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 650339 - Allow access to UI on pages that consume touch events and prevent panning

Stage 5: Release

10. Landing criteria

` {{#set:Feature open issues and risks=* bug 653009 - Make preventDefault for touch events compatible with WebKit/Opera |Feature overview=Expose touch events to content for better interaction with web pages and services, and compatibility with WebKit/Opera and existing web content. |Feature users and use cases=* Expose single-touch events to content in Fennec.

  • Don't let pages completely block navigation or sidebar panning.
  • Compatibility with existing pages like Google Maps.
  • Conformance with a subset of W3C Touch Events editor's draft.
  • Compatibility with a common subset of Safari/Android/WebKit functionality.

|Feature dependencies=` |Feature requirements=* No performance regressions on non-touch-event pages.

  • Acceptable performance of touch events in content. (Need more precise criteria?)
  • Sidebar (or some alternate form of navigation) is still accessible on pages that use touch events.

|Feature non-goals=* Expose multiple simultaneous touches to content (will be done in a part 2).

  • 100% conformance with W3C Touch Events spec (will be completed in future versions).
  • 100% compatibility with Safari or other browsers.
  • Enable W3C touch events in desktop Firefox (will be done in future versions).

|Feature functional spec=` |Feature ux design=` |Feature implementation plan=` |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=* QA Test Plan |Feature operations review=` |Feature implementation notes=* bug 544614 - Tracking bug for touch events in Fennec

  • bug 650339 - Allow access to UI on pages that consume touch events and prevent panning

|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-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=` }}


Other documentation

Retrieved from "https://wiki.mozilla.org/index.php?title=Fennec/Features/touch&oldid=357776"