canmove, Confirmed users, Bureaucrats and Sysops emeriti
2,798
edits
Mobile/UX/VirtualKeyboard: Difference between revisions
Jump to navigation
Jump to search
no edit summary
MarkFinkle (talk | contribs) (Created page with "Documenting the UX conventions regarding how the virtual keyboard interacts with the UI. You'll fnd that the conventions are grouped into '''General Guidelines''' and '''Awesomeb...") |
MarkFinkle (talk | contribs) No edit summary |
||
| Line 12: | Line 12: | ||
The VKB should not close when: | The VKB should not close when: | ||
* A tab is opened in background | * A tab is opened in background | ||
* It is already open and the user | * It is already open and the user pans a list | ||
* It is already opened and the user decide to pan the content | * It is already opened and the user decide to pan the content | ||
* The user touches another textbox without releasing - as can happen when panning | * The user touches another textbox without releasing - as can happen when panning | ||
Basically the VKB should stay active if the user does _not_ dismiss it intentionally. | Basically the VKB should stay active if the user does _not_ dismiss it intentionally. | ||
===Awesomebar Exceptions=== | |||
The VKB reduces the screen space available to the awesomebar screen. There are some exceptions to the general guidelines, created to maximize the effectiveness of the awesomebar screen. | |||
* The VKB should close if the user pans the awesomebar results list | |||