GNOME Bugzilla – Bug 609356
Ending zooming in with vertical scroll over a window in the overview is broken
Last modified: 2010-02-08 20:51:18 UTC
1) When the mouse is released after the user is done zooming in with vertical scroll over a window in the overview, the overview is existed and that window is switched to. We need to fix it to not ignore the mouse being released in that case. 2) Hitting Esc while zooming in with vertical scroll, escapes the overview and leaves the desktop in a broken state, with the following message printed: (mutter:17988): Clutter-WARNING **: Actor of type ClutterGroup is not inside a container Further attempts to activate the Activities button cause the following error: JS ERROR: !!! Exception was: TypeError: this._dragActor.get_stage() is null JS ERROR: !!! lineNumber = '222' JS ERROR: !!! fileName = '/home/mazik/gnome-shell/source/gnome-shell/js/ui/dnd.js' JS ERROR: !!! message = 'this._dragActor.get_stage() is null' JS ERROR: !!! stack = '([object _private_Clutter_Event])@/home/mazik/gnome-shell/source/gnome-shell/js/ui/dnd.js:222 ([object _private_Clutter_Rectangle],[object _private_Clutter_Event])@/home/mazik/gnome-shell/source/gnome-shell/js/ui/dnd.js:107 ([object _private_Clutter_Rectangle],[object _private_Clutter_Event])@/home/mazik/gnome-shell/source/gnome-shell/js/ui/dnd.js:24 Error("Chained exception")@:0 ("Chained exception")@gjs_throw:0 Hitting Esc while using that feature should bring the window back to its normal preview state.
(In reply to comment #0) > 1) When the mouse is released after the user is done zooming in with vertical > scroll over a window in the overview, the overview is existed and that window > is switched to. We need to fix it to not ignore the mouse being released in > that case. This is with a mouse with a scroll wheel that also can be pressed to act as a middle mouse button? And you are pressing it when scrolling? Presumably we just need to check and only allow button 1 when clicking on windows.
Marking as a duplicate of a very closely related bug *** This bug has been marked as a duplicate of bug 609243 ***
(In reply to comment #1) > (In reply to comment #0) > > 1) When the mouse is released after the user is done zooming in with vertical > > scroll over a window in the overview, the overview is existed and that window > > is switched to. We need to fix it to not ignore the mouse being released in > > that case. > > This is with a mouse with a scroll wheel that also can be pressed to act as a > middle mouse button? And you are pressing it when scrolling? > > Presumably we just need to check and only allow button 1 when clicking on > windows. That was actually me holding the left mouse button while using the vertical scroll. I didn't realize it would just work without the button pressed. Also, my comment above should be "We need to fix it to *ignore* the mouse being released in that case."
(In reply to comment #3) > (In reply to comment #1) > > (In reply to comment #0) > > > 1) When the mouse is released after the user is done zooming in with vertical > > > scroll over a window in the overview, the overview is existed and that window > > > is switched to. We need to fix it to not ignore the mouse being released in > > > that case. > > > > This is with a mouse with a scroll wheel that also can be pressed to act as a > > middle mouse button? And you are pressing it when scrolling? > > > > Presumably we just need to check and only allow button 1 when clicking on > > windows. > > That was actually me holding the left mouse button while using the vertical > scroll. I didn't realize it would just work without the button pressed. > > Also, my comment above should be "We need to fix it to *ignore* the mouse being > released in that case." Hmm, any idea how you got the idea that you needed to hold the left mouse button down? I'm not really sure what should happen in that case (probably should select the window if you release on top of the window, not if you mouse away from the window), but it seems like a real corner case and I'm not sure it's worth code.
No idea, probably to indicate selection, kind of like you do it with dragging. Sure, I agree it is a corner case and might not be worth code.