Separate UI navigation and text-entry keyboards
Registered by
Jorge Silva
Currently, the keyboard contains both text-entry and UI-navigation keys. This works, but is a bit of a waste of time and precious space. The UI-navigation and text-entry layouts should be displayed separately. The UI-layout would be the default while the text-entry layout would be available on command, or when a widget that requires text-entry is focused.
Blueprint information
- Status:
- Complete
- Approver:
- Jorge Silva
- Priority:
- Undefined
- Drafter:
- Jorge Silva
- Direction:
- Needs approval
- Assignee:
- Eric Wan
- Definition:
- Approved
- Series goal:
- None
- Implementation:
- Implemented
- Milestone target:
- None
- Started by
- Jorge Silva
- Completed by
- Jorge Silva
Related branches
Related bugs
Sprints
Whiteboard
Pushed it into Android v0.1-alpha release. The full keyboard was split into separate UI navigation and text-entry keyboards.
(?)