Activity log for bug #1447886

Date Who What changed Old value New value Message
2015-04-24 03:17:16 Daniel van Vugt bug added bug
2015-04-24 03:17:25 Daniel van Vugt bug task added mir
2015-04-24 03:17:33 Daniel van Vugt mir: importance Undecided Medium
2015-04-24 03:17:36 Daniel van Vugt mir: status New Triaged
2015-04-24 03:17:39 Daniel van Vugt mir (Ubuntu): status New Invalid
2015-04-24 03:17:55 Daniel van Vugt description mir_demo_server(_minimal): Window movement/resizing stops responding when the cursor leaves the surface. If you move or resize a surface with Alt+(button1/button3) then it's very easy to get the shell into a state where the window stops responding to movement/resizing and even becomes unrecoverable. Essentially the problem is the shell is only looking at the current cursor position and doesn't do anything if it's outside of the surface. This is frustrating as waiving the mouse around a bit it's very easy to reach this situation. It should be looking at the gesture as a whole and only doing position checking at the start of the move/resize gesture (ie. mouse button down). Thereafter the gesture should be continuous until the button is released, regardless of whether the cursor is still inside the surface/titlebar. You will find this is how all real desktops work, and mir_proving_server tries to too. Surfaces should always "own" input regardless of cursor position, just so long as the gesture (mouse down) began on that surface. The "unrecoverable" bit: This happens if you resize a surface too small/thin and it becomes impossible to resize it bigger again. mir_demo_server(_minimal) version 0.13 and later: Window movement/resizing stops responding when the cursor leaves the surface. If you move or resize a surface with Alt+(button1/button3) then it's very easy to get the shell into a state where the window stops responding to movement/resizing and even becomes unrecoverable. Essentially the problem is the shell is only looking at the current cursor position and doesn't do anything if it's outside of the surface. This is frustrating as waiving the mouse around a bit it's very easy to reach this situation.  It should be looking at the gesture as a whole and only doing position checking at the start of the move/resize gesture (ie. mouse button down). Thereafter the gesture should be continuous until the button is released, regardless of whether the cursor is still inside the surface/titlebar. You will find this is how all real desktops work, and mir_proving_server tries to too. Surfaces should always "own" input regardless of cursor position, just so long as the gesture (mouse down) began on that surface. The "unrecoverable" bit: This happens if you resize a surface too small/thin and it becomes impossible to resize it bigger again.
2015-04-24 03:18:35 Daniel van Vugt description mir_demo_server(_minimal) version 0.13 and later: Window movement/resizing stops responding when the cursor leaves the surface. If you move or resize a surface with Alt+(button1/button3) then it's very easy to get the shell into a state where the window stops responding to movement/resizing and even becomes unrecoverable. Essentially the problem is the shell is only looking at the current cursor position and doesn't do anything if it's outside of the surface. This is frustrating as waiving the mouse around a bit it's very easy to reach this situation.  It should be looking at the gesture as a whole and only doing position checking at the start of the move/resize gesture (ie. mouse button down). Thereafter the gesture should be continuous until the button is released, regardless of whether the cursor is still inside the surface/titlebar. You will find this is how all real desktops work, and mir_proving_server tries to too. Surfaces should always "own" input regardless of cursor position, just so long as the gesture (mouse down) began on that surface. The "unrecoverable" bit: This happens if you resize a surface too small/thin and it becomes impossible to resize it bigger again. mir_demo_server(_minimal) version 0.13 and later: Window movement/resizing stops responding when the cursor leaves the surface. If you move or resize a surface with Alt+(button1/button3) then it's very easy to get the shell into a state where the window stops responding to movement/resizing and even becomes unrecoverable. Essentially the problem is the shell is only looking at the current cursor position and doesn't do anything if it's outside of the surface. This is frustrating as waiving the mouse around a bit it's very easy to reach this situation. It should be looking at the gesture as a whole and only doing position checking at the start of the move/resize gesture (ie. mouse button down). Thereafter the gesture should be continuous until the button is released, regardless of whether the cursor is still inside the surface/titlebar. You will find this is how all real desktops work, and mir_proving_server tries to too. Surfaces should always "own" input regardless of cursor position, just so long as the gesture (mouse down) began on that surface. The "unrecoverable" bit: This happens if you resize a surface too small/thin and it becomes impossible to resize it bigger again.
2015-04-24 03:19:22 Daniel van Vugt tags wm
2015-10-09 09:08:24 Daniel van Vugt mir (Ubuntu): status Invalid Triaged
2015-10-09 09:08:30 Daniel van Vugt mir (Ubuntu): importance Undecided Medium
2015-10-09 09:08:47 Daniel van Vugt description mir_demo_server(_minimal) version 0.13 and later: Window movement/resizing stops responding when the cursor leaves the surface. If you move or resize a surface with Alt+(button1/button3) then it's very easy to get the shell into a state where the window stops responding to movement/resizing and even becomes unrecoverable. Essentially the problem is the shell is only looking at the current cursor position and doesn't do anything if it's outside of the surface. This is frustrating as waiving the mouse around a bit it's very easy to reach this situation. It should be looking at the gesture as a whole and only doing position checking at the start of the move/resize gesture (ie. mouse button down). Thereafter the gesture should be continuous until the button is released, regardless of whether the cursor is still inside the surface/titlebar. You will find this is how all real desktops work, and mir_proving_server tries to too. Surfaces should always "own" input regardless of cursor position, just so long as the gesture (mouse down) began on that surface. The "unrecoverable" bit: This happens if you resize a surface too small/thin and it becomes impossible to resize it bigger again. mir_demo_server(_minimal) version 0.13 and later: Window movement/resizing stops responding when the cursor leaves the surface. If you move or resize a surface with Alt+(button1/button3) then it's very easy to get the shell into a state where the window stops responding to movement/resizing and even becomes unrecoverable (window 1px wide). Essentially the problem is the shell is only looking at the current cursor position and doesn't do anything if it's outside of the surface. This is frustrating as waiving the mouse around a bit it's very easy to reach this situation. It should be looking at the gesture as a whole and only doing position checking at the start of the move/resize gesture (ie. mouse button down). Thereafter the gesture should be continuous until the button is released, regardless of whether the cursor is still inside the surface/titlebar. You will find this is how all real desktops work, and mir_proving_server tries to too. Surfaces should always "own" input regardless of cursor position, just so long as the gesture (mouse down) began on that surface. The "unrecoverable" bit: This happens if you resize a surface too small/thin and it becomes impossible to resize it bigger again.
2015-10-09 09:09:30 Daniel van Vugt summary mir_demo_server(_minimal): Window movement/resizing stops responding when the cursor leaves the surface mir_demo_server(_minimal): Window movement/resizing stops responding when the cursor leaves the surface, and can lead to windows 1px wide and unrecoverable.
2016-04-26 08:51:25 Alan Griffiths mir (Ubuntu): status Triaged Fix Released
2016-04-26 08:51:29 Alan Griffiths mir: status Triaged Fix Released
2016-04-26 08:53:57 Daniel van Vugt mir: status Fix Released Triaged
2016-04-26 08:54:01 Daniel van Vugt mir (Ubuntu): status Fix Released Triaged
2016-04-27 14:22:27 Alan Griffiths bug task added miral
2016-04-27 14:22:39 Alan Griffiths miral: status New Confirmed
2016-04-27 14:22:44 Alan Griffiths miral: importance Undecided Medium
2016-04-27 14:22:46 Alan Griffiths miral: assignee Alan Griffiths (alan-griffiths)
2016-04-27 14:22:54 Alan Griffiths branch linked lp:~alan-griffiths/miral/revised-resize
2016-04-28 09:09:45 Alan Griffiths branch linked lp:~alan-griffiths/mir/fix-1447886
2016-04-28 09:18:38 Alan Griffiths mir: milestone 0.23.0
2016-04-28 09:18:42 Alan Griffiths mir: assignee Alan Griffiths (alan-griffiths)
2016-04-28 09:18:47 Alan Griffiths mir: status Triaged In Progress
2016-04-28 09:18:55 Alan Griffiths miral: status Confirmed In Progress
2016-04-29 09:25:23 Mir CI Bot mir: status In Progress Fix Committed
2016-06-02 21:57:24 Launchpad Janitor branch linked lp:~untrusted-ci-dev-bot/mir/mir-ubuntu-yakkety-landing-005
2016-06-08 13:30:27 Daniel van Vugt mir: status Fix Committed Fix Released
2016-06-08 14:45:26 Launchpad Janitor mir (Ubuntu): status Triaged Fix Released
2016-06-09 13:23:12 Alan Griffiths miral: status In Progress Fix Committed
2016-09-22 11:11:58 Alan Griffiths miral: status Fix Committed Fix Released
2017-06-05 11:01:50 Launchpad Janitor branch linked lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736