Issue with window snapping animation after a window has been maximized

Bug #1450650 reported by Morgan Risch
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Gala
New
Undecided
Unassigned

Bug Description

When you first open an app (ie. Files) and drag it to the side of a screen to snap it to that half the animation is fine, but if you maximize that app and then afterward snap it to one half of the screen the window jumps to the center of the screen and then snaps to the edge of the screen. This is especially noticeable in the browser which I use maximized and snapped to either side of the screen often.

affects: elementaryos → gala
Revision history for this message
robzi (robert-zim) wrote :

I am also affected by this bug. The below is what I wrote in the elementary os stackexchange (which was the wrong forum).

##############
After I maximize a window and then unmaximize it, the snap animation becomes weird. It seems like the window position of the unmaximized window becomes the starting position for the snap animation. This occurs for all windows.

Example with Files: 1. Open Files 2. Maximize Files 3. Snap the window to the right. 4. Snap the window to the left. Notice the faulty animation.

You can observe the correct snap behaviour if you don't maximize the window first.

Example with Files, correct behaviour: 1. Open Files 2. Alternate between snapping to the right and left. Notice the fluid and correct animations.

I'm using the included intel graphics driver and have a nvidia card turned off in the "Nvidia x server settings".
##############

Revision history for this message
robzi (robert-zim) wrote :

I will soon follow up with a video of the problem.

Revision history for this message
robzi (robert-zim) wrote :

Here is a video of the bug.

Revision history for this message
Jorge Curiel (yorchi) wrote :

I can confirm this happens to me.

I can replicate it with Chromium and Files.

I have an intel graphics card and my screen resolution is 1366 x 768

Revision history for this message
Schievenin Eric (eric-schievenin) wrote :

The exact same problem affects me too. I only have one graphics card : Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09).

Revision history for this message
Tom Beckmann (tombeckmann) wrote :

This is in fact a known problem due to the way snapping is implemented. We have no way of knowing what the CSD dimensions are like until we get the form once, so we can only properly animate windows that have been unmaximized at some point. Unless there are some (probably rather big) API changes in gtk/mutter, we probably can't fix this either, at least I couldn't figure out a way to use the currently available API to workaround this problem. Only option we have would be to disable snapping animations all together on windows that have never been unmaximized.

Revision history for this message
robzi (robert-zim) wrote :

But the problem doesn't occur when the window never was mazimized. Wouldn't it be possible to give the window the state it had before it was maximized when you unmaximize it?

If there was a way to entirely disable the snap animations (and keep all the other animations) I would rather have that than the current behaviour. It is very distracting.

Revision history for this message
Morgan Risch (morgan-risch) wrote :

Not an issue on loki-beta1 as snapping animations have been disabled.

I Personally like having snapping animations off. I like the approach unity takes with an animated box outlining where the window is being snapped. Adds an animated feel without an actual slow snapping animation.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.