Fennec/Features/touch: Difference between revisions

no edit summary
No edit summary
 
(32 intermediate revisions by 8 users not shown)
Line 1: Line 1:
<section begin="status" />
{{FeatureStatus
{| class="fullwidth-table"
|Feature name=Touch Events part 1: single-touch
|-
|Feature stage=Shipped
| style="font-weight: bold; background: #DDD;" | Feature  
|Feature version=Firefox 6
| style="font-weight: bold; background: #DDD;" | Status
|Feature health=OK
| style="font-weight: bold; background: #DDD;" | ETA
}}
| style="font-weight: bold; background: #DDD;" | Owner
{{FeatureTeam
|-
|Feature product manager=Thomas Arend
<section begin="status" />
|Feature feature manager=Matt Brubeck
| [[Fennec/Features/touch|Touch Events]]
|Feature lead engineer=Wes Johnson, Olli Pettay, Matt Brubeck
| {{StatusHealthy|status=Implementation in progress}}
|Feature qa lead=Martijn Wargers
| 2011-07-01
}}
| Thomas Arend
{{FeaturePageBody
<section end="status" />
|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.
== 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  ==
 
* Finish patches and get reviews.
* Write automated tests and do manual compatibility testing.
* Experiment with different ways of allowing sidebar panning.
* Performance testing and optimization.
* Send spec feedback to W3C Web Events working group.
 
== Open Issues  ==
 
 
== Related Bugs &amp; Dependencies  ==
 
* {{bug|544614}} - Tracking bug for touch events in Fennec
 
== Designs  ==
Possible new gesture set, as mapped to current browser features:
 
'''[Browser Feature] = [Gesture]'''
 
Back = Double-finger Swipe Left  + Onscreen Back button
Forward = Double-finger Swipe Right + Onscreen Forward button
Scroll Down = Swipe Down
 
Scroll Up = Swipe Up
 
Pan =
 
== Test Plans  ==
 
 
== Goals/Use Cases  ==
 
* Expose single-touch events to content in Fennec.
* Don't let pages completely block navigation or sidebar panning.
* Don't let pages completely block navigation or sidebar panning.
* Compatibility with existing pages like Google Maps.
* Compatibility with existing pages like Google Maps.
* Conformance with a subset of [http://dvcs.w3.org/hg/webevents/raw-file/tip/touchevents.html W3C Touch Events editor's draft].
* Conformance with a subset of [http://dvcs.w3.org/hg/webevents/raw-file/tip/touchevents.html W3C Touch Events editor's draft].
* Compatibility with a common subset of Safari/Android/WebKit functionality.
* Compatibility with a common subset of Safari/Android/WebKit functionality.
 
|Feature requirements=* No performance regressions on non-touch-event pages.
== Non-Goals  ==
* 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.
* Expose multiple simultaneous touches to content (will be done in a future version).
|Feature non-goals=* Expose multiple simultaneous touches to content (will be done in a [[Fennec/Features/multitouch|part 2]]).
* 100% conformance with W3C Touch Events spec (will be completed in future versions).
* 100% conformance with W3C Touch Events spec (will be completed in future versions).
* 100% compatibility with Safari or other browsers.
* 100% compatibility with Safari or other browsers.
* Enable W3C touch events in desktop Firefox (will be done in future versions).
* Enable W3C touch events in desktop Firefox (will be done in future versions).
|Feature qa review=* [[Fennec/Features/touch/TestPlan|QA Test Plan]]
|Feature implementation notes=* {{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]].


== Other Documentation  ==
* {{bug|650339}} - Allow access to UI on pages that consume touch events and prevent panning
 
}}
{{FeatureInfo
|Feature priority=P1
|Feature roadmap=Firefox Mobile
|Feature list=Mobile
|Feature engineering team=Mobile platform
}}
{{FeatureTeamStatus
|Feature security status=sec-review-unnecessary
|Feature security health=OK
}}
== Other documentation ==
* [http://digdug2k.wordpress.com/2011/05/02/touchevents/ Blog post about touch events in mobile Firefox]
* [http://dvcs.w3.org/hg/webevents/raw-file/tip/touchevents.html W3C Touch Events editor's draft specification]
* [http://dvcs.w3.org/hg/webevents/raw-file/tip/touchevents.html W3C Touch Events editor's draft specification]
== Legend (remove if you like)  ==
{| class="fullwidth-table"
|-
| {{StatusHealthy|status=&nbsp;}}
| Healthy: feature is progressing as expected.
|-
| {{StatusBlocked|status=&nbsp;}}
| Blocked: feature is currently blocked.
|-
| {{StatusAtRisk|status=&nbsp;}}
| 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.
|}
__NOTOC__
[[Category:Features]] [[Category:Mobile]] [[Category:Firefox]] [[Category:Priority_1]] [[Category:Platform]] [[Category:UX]]
canmove, Confirmed users, Bureaucrats and Sysops emeriti
2,776

edits