After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 590410 - Resizing windows too quickly destroys extra resize area
Resizing windows too quickly destroys extra resize area
Status: RESOLVED FIXED
Product: metacity
Classification: Other
Component: general
2.27.x
Other All
: Normal minor
: ---
Assigned To: Thomas Thurman
Metacity maintainers list
Depends on:
Blocks:
 
 
Reported: 2009-07-31 20:23 UTC by Oliver Joos
Modified: 2009-11-18 11:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description Oliver Joos 2009-07-31 20:23:15 UTC
Please describe the problem:
Affected apps are for example nautilus and gedit. It's a first guess that this bug is in metacity. It's most obvious on systems with slow graphic hardware and a touchpad.


Steps to reproduce:
1. Start app with extra resize area in lower right corner (nautilus, gedit, ...)
2. Resize its window and release left mouse button WHILE the mouse still moves!
3. Try to grab the square extra resize area again


Actual results:
The extra resize area has gone. It reappears when resizing the window again by first stopping the mouse, then releasing the left button.

Expected results:
I expect the resize area always to be bound to its visual part.

Does this happen every time?
Yes, if you exactly follow step 1-3 above. In everyday usage it might seem to be random.

Other information:
I think, when the button is released while moving the mouse, first the window gets redrawn for the last time AND AFTER THAT the mouse coordinates are read to determine where the extra resize area shall be, and after clipping this area to its usual region it disappears completely.

See also:
  https://bugs.launchpad.net/bugs/282013

Related bugs: (no duplicates)
  http://bugzilla.gnome.org/show_bug.cgi?id=558811
  http://bugzilla.gnome.org/show_bug.cgi?id=559203
  http://bugzilla.gnome.org/show_bug.cgi?id=496536
Comment 1 Oliver Joos 2009-11-18 11:20:04 UTC
In 2.28.1 it seems to be fixed!