[UX/apps] OSK <> apps behavior is not clearly defined
Bug #1131249 reported by
Olivier Tilloy
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu UI Toolkit |
Fix Released
|
High
|
Florian Boucault | ||
Ubuntu UX |
Fix Released
|
High
|
Oren Horev | ||
ubuntu-ui-toolkit (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
In various applications (telephony, browser, …) where the OSK can be invoked, we are using a trick to ensure that the OSK doesn’t cover content: a KeyboardRectangle component whose height is "Qt.inputMethod
This means code duplication, and unnecessary logic to handle something that the window manager should be taking care of.
Related branches
lp:~renatofilho/ubuntu-ui-toolkit/fix-keyboard-visibility
- PS Jenkins bot: Approve (continuous-integration)
- Florian Boucault (community): Needs Fixing
-
Diff: 69 lines (+23/-0)3 files modifiedCHANGES (+1/-0)
components.api (+1/-0)
modules/Ubuntu/Components/MainView.qml (+21/-0)
summary: |
- [W/M] apps should be resized to accomodate for the OSK when shown + [W/M] apps should be resized to accomodate for the OSK when it’s visible |
Changed in ubuntu-ux: | |
assignee: | nobody → Rachel Liu (rachelliu) |
Changed in ubuntu-ux: | |
assignee: | Rachel Liu (rachelliu) → Oren Horev (oreneeshy) |
Changed in touch-preview-images: | |
importance: | Undecided → High |
affects: | touch-preview-images → ubuntu-ui-toolkit |
Changed in ubuntu-ui-toolkit: | |
assignee: | Thomas Voß (thomas-voss) → Florian Boucault (fboucault) |
Changed in ubuntu-ui-toolkit: | |
status: | Fix Committed → Fix Released |
Changed in ubuntu-ux: | |
status: | New → Fix Committed |
importance: | Undecided → High |
Changed in ubuntu-ux: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
In the same way we've decided against handling orientation on the WM level, I'm against having the OSK rectangle being respected like this.
Indeed we could provide ways that the MainView could, potentially by default, resize to accommodate for the keyboard rectangle, but apps need to be able to override that behaviour.
We also need defined the preferred User Experience - should the toolbar always be there on top of the OSK? If not - is the toolbar unavailable when the OSK is up? Is it always on screen (sacrificing screen real estate)? Is there a way to invoke / dismiss the toolbar when OSK is up?
If there's a text entry in the toolbar (like there is in the Browser) obviously it needs to be visible when typing, but maybe generic bottom bars should dismiss the keyboard when invoked?