[dialer app] + [window management] movement on screen in window mode
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Pocket Desktop |
New
|
Medium
|
Unassigned | ||
Ubuntu UX |
Triaged
|
High
|
Olga Kemmet | ||
unity8 (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
somewhat related to bug 1488852
so the dialer app is currently treated like any other window in terms of movement, you can move the dialer app to the point where the dialer application window is not seen "hanging of the screen" so only the title bar of the application is visible.
Also, if the device reboots, this will be the remembered location of the window.
Concern was that the user might move offscreen and struggle to find it quickly for "ending call" or entering numbers at a prompt or changing from loudspeaker to earpiece or wanting to hit mute.
It was discussed whether or not the dialer application should become a "special" application/surface to disallow having any portion of the window being moved offscreen ? Or is this completely ok - e.g. the user wanted to do it and should be allowed to.
Or should the green banner of the dialer app in the shell be used to bring the dialer app back on screen ?
Changed in canonical-pocket-desktop: | |
importance: | Undecided → High |
description: | updated |
Changed in ubuntu-ux: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Olga Kemmet (olga-kemmet) |
Changed in canonical-pocket-desktop: | |
importance: | High → Medium |
@kevin:
I had a chat with Matthew who is working on the MIR spec. One of the suggestions I had was to reposition the windows after a reboot. The ideal case would be to show the full window to the user, positioned as close as possible to its previous "off-screen" position. Many people, myself included, close and re-open apps because a window was moved too far out of view. In most cases this window is displayed fully on screen, close to the previous position.
That might solve part of the problem, at least after a reboot of the device. The indicator issue is part of an other bug, as mentioned above.