Gaia/System/Keyboard

Status

• Stage: Planning
• Release target: ?

Experiential in-homescreen keyboard and MozKeyboard API in place right now.

Team

• UX: Casey Yee (IRC: cyee)
• Eng: Tim Chien (IRC: timdream)

Reading

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.

• dev-b2g, counter-argument to have Gecko providing the keyboard: http://groups.google.com/group/mozilla.dev.b2g/msg/8ee52324ac24ab68

UX Requirements

• Keyboard hide/show behavior (needs to be outlined)
• Keyboard 'Enter' key should be labeled depending on entry context. For example 'Next' for next input field focus or 'Submit' for end of form.