Fennec/Features/androidcopypaste: Difference between revisions

Revision as of 21:00, 26 April 2011

Feature	Status	ETA	Owner
Android-style copy/paste	Concept	YYYY-MM-DD	Owner Name

Summary

Implement Gingerbread-style copy and paste

Team

Who's working on this?

Feature Manager: tbd?
Lead Developer:
Product Manager:
QA:
UX: Madhava, Ian
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

bug 652168 - Add cursor positioning thumb controls to edit boxes

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

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.

Ian will be creating the necessary visual assets.

Use Cases

Test Plans

Any and all test plans and strategies. Either inline or linked to.

Goals

Non-Goals

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.

@@ Line 1: / Line 1: @@
+<section begin="status" />
 {| class="fullwidth-table"
 |-
 | style="font-weight: bold; background: #DDD;" | Feature
 | style="font-weight: bold; background: #DDD;" | Status
 | style="font-weight: bold; background: #DDD;" | ETA
 | style="font-weight: bold; background: #DDD;" | Owner
 |-
-<section begin="status" />
+| [[Fennec/Features/androidcopypaste|Android-style copy/paste]]
-| [[Fennec/Features/androidcopypaste|Android-style copy/paste]]
+| {{StatusHealthy|status=Concept}}
-| {{StatusHealthy|status=Concept}}
+| YYYY-MM-DD
-| YYYY-MM-DD
+| Owner Name
-| Owner Name
+<section end="status" />
-<section end="status" />
-|-
 |}
-== Summary ==
+== Summary  ==
-Implement Gingerbread-style copy and paste
-== Team ==
+Implement Gingerbread-style copy and paste
-Who's working on this?
-* '''Feature Manager''': ''tbd?''
+== Team  ==
-* '''Lead Developer''':
-* '''Product Manager''':
-* '''QA''':
-* '''UX''': Madhava
-* '''Security''':
-* Etc.
+Who's working on this?
-== Release Requirements ==
+*'''Feature Manager''': ''tbd?''
-Complete checklist of items that need to be satisfied before we can call this feature "done".
+*'''Lead Developer''':
+*'''Product Manager''':
+*'''QA''':
+*'''UX''': Madhava, Ian
+*'''Security''':
+*Etc.
-== Next Steps ==
+<br>
-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 ==
+== Release Requirements  ==
-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 ==
+Complete checklist of items that need to be satisfied before we can call this feature "done".
-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.
+== 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 &amp; Dependencies  ==
+* {{bug|652168}} - Add cursor positioning thumb controls to edit boxes
 == Designs  ==
@@ Line 48: / Line 55: @@
 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>
 <br>
-== Use Cases ==
+Ian will be creating the necessary visual assets.
-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 ==
+== Use Cases  ==
-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 ==
+== Test Plans  ==
-Things we are specifically not doing or building as part of this feature.
-== Other Documentation ==
+Any and all test plans and strategies. Either inline or linked to.
-Can include things like:
-* Competitive landscape
+== Goals  ==
-* Research & references
-* Whatever else is useful to the project.
+== Non-Goals  ==
+== Other Documentation  ==
+Can include things like:
+*Competitive landscape
+*Research &amp; references
+*Whatever else is useful to the project.
+== Legend (remove if you like)  ==
-== 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:Features]] [[Category:Mobile]]
-[[Category:Mobile]]