Mobile/Archive/Virtual Keyboard
< Mobile
Summary
We're not implementing our own soft keyboard - Fennec will use the native soft keyboard on all platforms.
This project is to make sure that our UI is usable and effective even when a softkeyboard is deployed and so is taking much of the screen real estate.
In practice, this will be the result of three design areas:
- in general, only bringing up the keyboard when it's actually wanted (not prematurely, if the browser is making on-screen suggestions first)
- making sure that our UI is not obscured by the on-screen keyboard
- altering the mechanism by which people select a search engine, so that it's only on screen when it has to be -- this is so that we can use the sliver of the awesomescreen that is visible (esp. in landscape) when the user is typing for awesome-suggestions.
Current Status
Next Steps
Related Bugs
Team
- Project Lead:
Designs
Proposals: