|
|
| Line 1: |
Line 1: |
| ==Status== | | ==Status & Team== |
|
| |
|
| * Stage: Planning | | * See: https://docs.google.com/spreadsheet/ccc?key=0AiBigu584YY7dGlNSlY0QzhJb3M5anRBa1gxalV0Y3c#gid=0 |
| * Release target: ?
| |
|
| |
|
| Experiential in-homescreen keyboard and MozKeyboard API in place right now.
| | =UI= |
| | ==Requirements== |
|
| |
|
| == Team ==
| | * User can hide and show keyboard |
| | * Keyboard 'Enter' key should be labeled depending on entry context. For example, 'Next' for next input field focus or 'Submit' for end of form. |
| | * . . . |
|
| |
|
| * UX: Casey Yee (IRC: cyee)
| |
| * Eng: Tim Chien (IRC: timdream)
| |
|
| |
|
| == Reading == | | =Auto-correct= |
| | ==Requirements== |
| | * . . . |
|
| |
|
| The plan is to allow user to add/remove their own keyboard and input method, from third party. The keyboards will be in their individual iframes just like how Open Web Apps gets to load into Gaia. [owa-keyboard]
| |
|
| |
|
| The exact way for the keyboard to communicate with the system is still in planning phrase.
| | =Cursor= |
| | ==Requirements== |
| | * . . . |
|
| |
|
| * dev-b2g, counter-argument to have Gecko providing the keyboard: http://groups.google.com/group/mozilla.dev.b2g/msg/8ee52324ac24ab68
| |
|
| |
|
| == UX Requirements == | | =Selection= |
| * Keyboard hide/show behavior (needs to be outlined) | | ==Requirements== |
| * Keyboard 'Enter' key should be labeled depending on entry context. For example 'Next' for next input field focus or 'Submit' for end of form.
| | * . . . |
|
| |
|
| ==Overview==
| |
|
| |
|
| ==Questions== | | =Copy/paste= |
| | | ==Requirements== |
| ==Next Steps== | | * . . . |