Fennec/Features/androidcopypaste: Difference between revisions

← Older edit

Fennec/Features/androidcopypaste (view source)

Revision as of 17:53, 18 August 2011

172 bytes removed , 18 August 2011

status updates

Mbrubeck

canmove, Confirmed users

1,584

edits

@@ 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" />
+}}
-| [[Android 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
+|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.
-== Summary ==
+This page here has a description of the behavior: http://developer.android.com/sdk/android-2.3-highlights.html
-Implement Gingerbread-style copy and paste
+<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>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>
-== Team ==
-Who's working on this?
-* '''Feature Manager''': ''tbd?''
+<b>Text Overflow</b>
-* '''Lead Developer''':
-* '''Product Manager''':
-* '''QA''':
-* '''UX''': Madhava
-* '''Security''':
-* Etc.
+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
-== Release Requirements ==
+. Pressing and holding to activate a cursor, and then dragging that cursor to the edge of the field to scroll text.
-Complete checklist of items that need to be satisfied before we can call this feature "done".
-== Next Steps ==
+. Dragging the text back and forth through the field, and then long pressing to insert a cursor.
-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.
+|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.
-== Open Issues ==
+* {{bug|652168}} - Add cursor positioning thumb controls to edit boxes
-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.
+* <s>{{bug|661388}}</s> (FIXED) - Support selecting text in web content
+* <s>{{bug|659022}}</s> (FIXED) - Implement copy from content
-== 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.
+{{FeatureInfo
+|Feature priority=P2
-== Designs ==
+|Feature roadmap=Firefox Mobile
-Any and all mockups, design specs, tech specs, etc.  Either inline or linked to.
+|Feature list=Mobile
+|Feature engineering team=Mobile front-end
-== 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.
+{{FeatureTeamStatus
+|Feature security status=sec-review-complete
-== Test Plans ==
+|Feature security health=OK
-Any and all test plans and strategies.  Either inline or linked to.
+|Feature security notes=reviewed by: imelven
+}}
-== 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 ==
-Can include things like:
-* Competitive landscape
-* Research & references
-* Whatever else is useful to the project.
-== 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]]