Fennec/Features/androidcopypaste: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(status updates)
 
(19 intermediate revisions by 9 users not shown)
Line 1: Line 1:
{| class="fullwidth-table"
{{FeatureStatus
|-
|Feature name=Android-style text selection handles
| style="font-weight: bold; background: #DDD;" | Feature
|Feature stage=Landed
| style="font-weight: bold; background: #DDD;" | Status
|Feature status=Complete
| style="font-weight: bold; background: #DDD;" | ETA
|Feature version=Firefox 7
| style="font-weight: bold; background: #DDD;" | Owner
|Feature health=OK
|-
|Feature status note=Some follow-up bugs being fixed in Firefox 8 and 9
<section begin="status" />
}}
| [[Fennec/Features/androidcopypaste|Android-style copy/paste]]
{{FeatureTeam
| {{StatusHealthy|status=Concept}}
|Feature product manager=Thomas Arend
| YYYY-MM-DD
|Feature feature manager=Thomas Arend
| Owner Name
|Feature lead engineer=Mark Finkle
<section end="status" />
|Feature qa lead=Aaron Train
|-
|Feature ux lead=Madhava Enros, Ian Barlow
|}
}}
 
{{FeaturePageBody
== Summary ==
|Feature ux design=If we could use the native method, we'd do so, so, instead, we have to mimic it, much as we do with the Android Menu.  
Implement Gingerbread-style copy and paste
 
== Team ==
Who's working on this?
 
* '''Feature Manager''': ''tbd?''
* '''Lead Developer''':
* '''Product Manager''':
* '''QA''':
* '''UX''': Madhava
* '''Security''':
* Etc.
 
 
== Release Requirements ==
Complete checklist of items that need to be satisfied before we can call this feature "done". 
 
== Next Steps ==
Either the next set of tasks that need to happen to move this project along, or (ideally) the full list of project tasks/action items with things crossed off as they're finished.  Including the name of who's responsible for each item, and a rough ETA can be useful.
 
== Open Issues ==
Unanswered questions, things that need to be explored, decisions that still need to be made, etc.  Again, including the name of who's responsible for each item can be useful.
 
== Related Bugs & Dependencies ==
Links to the feature tracking bug & other relevant bugs; links to related plans (test plan, product marketing plan, etc.); notes about things that depend on this, etc.
 
== Designs  ==
 
If we could use the native method, we'd do so, so, instead, we have to mimic it, much as we do with the Android Menu.  


This page here has a description of the behavior: http://developer.android.com/sdk/android-2.3-highlights.html  
This page here has a description of the behavior: http://developer.android.com/sdk/android-2.3-highlights.html  
<blockquote>One-touch word selection and copy/paste When entering text or viewing a web page, the user can quickly select a word by press-hold, then copy to the clipboard and paste. Pressing on a word enters a free-selection mode — the user can adjust the selection area as needed by dragging a set of bounding arrows to new positions, then copy the bounded area by pressing anywhere in the selection area. For text entry, the user can slide-press to enter a cursor mode, then reposition the cursor easily and accurately by dragging the cursor arrow. With both the selection and cursor modes, no use of a trackball is needed. <br></blockquote><blockquote>http://developer.android.com/sdk/images/2.3/onetouch.png &nbsp; http://developer.android.com/sdk/images/2.3/selection.png<br> </blockquote>
<blockquote>'''One-touch word selection and copy/paste'''<br>When entering text or viewing a web page, the user can quickly select a word by press-hold, then copy to the clipboard and paste. Pressing on a word enters a free-selection mode — the user can adjust the selection area as needed by dragging a set of bounding arrows to new positions, then copy the bounded area by pressing anywhere in the selection area.
<Br>
<br>http://developer.android.com/sdk/images/2.3/onetouch.png
<br>
<br>
<br>For text entry, the user can slide-press to enter a cursor mode, then reposition the cursor easily and accurately by dragging the cursor arrow. With both the selection and cursor modes, no use of a trackball is needed.
<br>
<br>http://developer.android.com/sdk/images/2.3/selection.png
</blockquote>


== Use Cases ==
Everyone loves use cases, so you should provide them if you can (and where it makes sense).  The [[ChannelSwitching/ChannelSwitchingFeature#Use_Cases|Channel Switcher]] Feature Page has some good examples.
== Test Plans ==
Any and all test plans and strategies.  Either inline or linked to.
== Goals ==
The high level goals for the feature (which the release requirements checklist should fulfill).  These are the guiding light and overall vision for the feature.  Refer to this if there is confusion or are disputes about direction, designs, planning, etc.
== Non-Goals ==
Things we are specifically not doing or building as part of this feature.


== Other Documentation ==
<b>Text Overflow</b>
Can include things like:
* Competitive landscape
* Research & references
* Whatever else is useful to the project.


== Legend (remove if you like) ==
We should also consider cases where text flows off the edge of a field, and how to get back to that to make changes. Android's native form fields handle this in two ways, as shown in this mockup: http://cl.ly/3y3u123U410L1L0u2W1n
{| 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__
1. Pressing and holding to activate a cursor, and then dragging that cursor to the edge of the field to scroll text.


2. Dragging the text back and forth through the field, and then long pressing to insert a cursor.
|Feature qa review=* [[Fennec/Features/androidcopypaste/TestPlan|QA Test Plan]]
|Feature implementation notes=Finkle has a restartless add-on that is being used to prototype the selection handle behavior and technical implementation.


[[Category:Features]]
* {{bug|652168}} - Add cursor positioning thumb controls to edit boxes
[[Category:Mobile]]
* <s>{{bug|661388}}</s> (FIXED) - Support selecting text in web content
* <s>{{bug|659022}}</s> (FIXED) - Implement copy from content
}}
{{FeatureInfo
|Feature priority=P2
|Feature roadmap=Firefox Mobile
|Feature list=Mobile
|Feature engineering team=Mobile front-end
}}
{{FeatureTeamStatus
|Feature security status=sec-review-complete
|Feature security health=OK
|Feature security notes=reviewed by: imelven
}}

Latest revision as of 17:53, 18 August 2011

Please use "Edit with form" above to edit this page.

Status

Android-style text selection handles
Stage Landed
Status Complete
Release target Firefox 7
Health OK
Status note Some follow-up bugs being fixed in Firefox 8 and 9

{{#set:Feature name=Android-style text selection handles

|Feature stage=Landed |Feature status=Complete |Feature version=Firefox 7 |Feature health=OK |Feature status note=Some follow-up bugs being fixed in Firefox 8 and 9 }}

Team

Product manager Thomas Arend
Directly Responsible Individual Thomas Arend
Lead engineer Mark Finkle
Security lead `
Privacy lead `
Localization lead `
Accessibility lead `
QA lead Aaron Train
UX lead Madhava Enros, Ian Barlow
Product marketing lead `
Operations lead `
Additional members `

{{#set:Feature product manager=Thomas Arend

|Feature feature manager=Thomas Arend |Feature lead engineer=Mark Finkle |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=Aaron Train |Feature ux lead=Madhava Enros, Ian Barlow |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=` }}

Open issues/risks

`

Stage 1: Definition

1. Feature overview

`

2. Users & use cases

`

3. Dependencies

`

4. Requirements

`

Non-goals

`

Stage 2: Design

5. Functional specification

`

6. User experience design

If we could use the native method, we'd do so, so, instead, we have to mimic it, much as we do with the Android Menu.

This page here has a description of the behavior: http://developer.android.com/sdk/android-2.3-highlights.html

One-touch word selection and copy/paste
When entering text or viewing a web page, the user can quickly select a word by press-hold, then copy to the clipboard and paste. Pressing on a word enters a free-selection mode — the user can adjust the selection area as needed by dragging a set of bounding arrows to new positions, then copy the bounded area by pressing anywhere in the selection area.



onetouch.png

For text entry, the user can slide-press to enter a cursor mode, then reposition the cursor easily and accurately by dragging the cursor arrow. With both the selection and cursor modes, no use of a trackball is needed.

selection.png


Text Overflow

We should also consider cases where text flows off the edge of a field, and how to get back to that to make changes. Android's native form fields handle this in two ways, as shown in this mockup: http://cl.ly/3y3u123U410L1L0u2W1n

1. Pressing and holding to activate a cursor, and then dragging that cursor to the edge of the field to scroll text.

2. Dragging the text back and forth through the field, and then long pressing to insert a cursor.

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

Finkle has a restartless add-on that is being used to prototype the selection handle behavior and technical implementation.

  • bug 652168 - Add cursor positioning thumb controls to edit boxes
  • bug 661388 (FIXED) - Support selecting text in web content
  • bug 659022 (FIXED) - Implement copy from content

Stage 5: Release

10. Landing criteria

` {{#set:Feature open issues and risks=` |Feature overview=` |Feature users and use cases=` |Feature dependencies=` |Feature requirements=` |Feature non-goals=` |Feature functional spec=` |Feature ux design=If we could use the native method, we'd do so, so, instead, we have to mimic it, much as we do with the Android Menu.

This page here has a description of the behavior: http://developer.android.com/sdk/android-2.3-highlights.html

One-touch word selection and copy/paste
When entering text or viewing a web page, the user can quickly select a word by press-hold, then copy to the clipboard and paste. Pressing on a word enters a free-selection mode — the user can adjust the selection area as needed by dragging a set of bounding arrows to new positions, then copy the bounded area by pressing anywhere in the selection area.



onetouch.png

For text entry, the user can slide-press to enter a cursor mode, then reposition the cursor easily and accurately by dragging the cursor arrow. With both the selection and cursor modes, no use of a trackball is needed.

selection.png


Text Overflow

We should also consider cases where text flows off the edge of a field, and how to get back to that to make changes. Android's native form fields handle this in two ways, as shown in this mockup: http://cl.ly/3y3u123U410L1L0u2W1n

1. Pressing and holding to activate a cursor, and then dragging that cursor to the edge of the field to scroll text.

2. Dragging the text back and forth through the field, and then long pressing to insert a cursor. |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=Finkle has a restartless add-on that is being used to prototype the selection handle behavior and technical implementation.

  • bug 652168 - Add cursor positioning thumb controls to edit boxes
  • bug 661388 (FIXED) - Support selecting text in web content
  • bug 659022 (FIXED) - Implement copy from content

|Feature landing criteria=` }}

Feature details

Priority P2
Rank 999
Theme / Goal `
Roadmap Firefox Mobile
Secondary roadmap `
Feature list Mobile
Project `
Engineering team Mobile front-end

{{#set:Feature priority=P2

|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 sec-review-complete reviewed by: 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-complete |Feature security health=OK |Feature security notes=reviewed by: 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=` }}