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 157826 - shift-locking during window move gets confused
shift-locking during window move gets confused
Status: RESOLVED DUPLICATE of bug 124582
Product: metacity
Classification: Other
Component: general
2.8.x
Other Linux
: Normal normal
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on:
Blocks:
 
 
Reported: 2004-11-10 05:21 UTC by Havoc Pennington
Modified: 2005-01-26 18:00 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Havoc Pennington 2004-11-10 05:21:20 UTC
See https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=132771

Steps to Reproduce:
1. Open two windows on the screen
2. Position window A so its upper-left corner is near the center of
the screen, with space above it to accomodate window B's entire height
3. Hold down Shift and position window B so its lower-left corner
rests on window A's upper-left corner
4. Continuing to hold down Shift, move window B straight up

Actual Results:  Window B temporarily jumps straight up, locking on to
the top edge of the screen (so its left edge remains aligned with
window A's left edge), then quickly jumps to one of the corners (as if
it "lost" its lock with the left edge of window A).

Expected Results:  Either moving window A up should cause it to
immediately jump into a locked position in the screen corner, or it
should remain "locked" against the left edge of window B (that it was
just previously locked against) against the top edge of the screen.
None of this jumping up, then a split second later jumping over.
Comment 1 Elijah Newren 2005-01-26 18:00:13 UTC
korn sun com pointed out the same bug, but in terms of using the arrow keys;
this bug didn't specify, but it sounds as though the mouse was being used. 
However, I have tested and both give the exact same behavior.  Anyway, I'm
marking this as a duplicate...

*** This bug has been marked as a duplicate of 124582 ***