Fennec/Features/touch: Difference between revisions
Jump to navigation
Jump to search
| Line 47: | Line 47: | ||
* See also [[Fennec/Features/gestures]]. | * See also [[Fennec/Features/gestures]]. | ||
* {{bug|650339 | * {{bug|650339}} - Allow access to UI on pages that consume touch events and prevent panning | ||
== Designs == | == Designs == | ||
Revision as of 21:31, 29 April 2011
| Feature | Status | ETA | Owner |
| Touch Events part 1: single-touch | Landed on 2011-04-29 - ready for testing | 2011-07-01 | Thomas Arend |
Summary
Expose touch events to content for better interaction with web pages and services, and compatibility with WebKit/Opera and existing web content.
Team
- Wes Johnson - Mobile Front-end
- Olli Pettay (smaug) - Platform
- Matt Brubeck - W3C spec
Release 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.
Next Steps
- Patches landed on 4/29 (will be in nightly builds on 2011-04-30).
- Begin testing, bug fixing, and tweaking.
- Finish patch for automated tests in bug 544614.
- Performance testing and optimization.
Open Issues
- bug 653009 - Make preventDefault for touch events compatible with WebKit/Opera
Related Bugs & Dependencies
- bug 544614 - Tracking bug for touch events in Fennec
- Patches and early test builds are available; see comments in this bug.
- See also Fennec/Features/gestures.
- bug 650339 - Allow access to UI on pages that consume touch events and prevent panning
Designs
Test Plans
Goals/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.
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).
Other Documentation
Legend (remove if you like)
| Healthy: feature is progressing as expected. | |
| Blocked: feature is currently blocked. | |
| At Risk: feature is at risk of missing its targeted release. | |
| ETA | Estimated date for completion of the current feature task. Overall ETA for the feature is the product release date. |