GNU bug report logs - #28620
Mouse drag event records wrong window for release when crossing frames

Previous Next

Full log

View this message in rfc822 format

From: Robert Weiner <rsw <at> gnu.org>
To: 28620 <at> debbugs.gnu.org
Cc: Eli Zaretskii <eliz <at> gnu.org>
Subject: bug#28620: Interact directly on Emacs bug#28620: mouse drag event records wrong release window
Date: Tue, 3 Oct 2017 14:21:43 -0400

[Message part 1 (text/plain, inline)]

Using the latest Emacs26 built from master on MacOS Sierra using the macOS
window system, I see the following if I have two frames: f1 and f2.

I start with the mouse within a window of f1 and selected frame of f1;
(mouse-position) also reports f1.

I click mouse-1 in an Emacs window of f2 and leave it there.
  (selected-frame) is now f2
  macOS window manager highlights f2 as active window
  (frame-focus) returns nil
  (mouse-position) reports a frame of f1       <<< WRONG


I click mouse-1 again in the same Emacs window of f2.
  (selected-frame) is still f2
  macOS window manager highlights f2 as active window
  (frame-focus) returns nil
  (mouse-position) now reports a frame of f2

This happens consistently in testing.  This must be a bug in mouse-position
for macOS, right?  Why would (mouse-position) still report f1 when f2 is
the selected frame?  Maybe this is why I am seeing the wrong frame on drag
releases too.

If anyone else could confirm this and whether it happens on other window
systems that use a mouse click to select windows, that would be helpful.

Bob

​​
​​

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.