283083 - focus-follows-mouse and autocomplete popup interact badly when popup pops up under mouse position

Status: RESOLVED WORKSFORME

(Core :: Widget: Gtk, defect)

Description

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

I use metacity as a window manager with the strict focus-follows-mouse setting.
 When the mouse is in a position that the autocomplete popup pops up under the
mouse pointer (1) keystrokes get lost and (2) the popup often disappears when it
should be showing

Steps to reproduce:
 1. run gconf-editor
 2. change apps/metacity/general/focus_mode to "mouse"
 3. run GTK2 Firefox
 4. enter a bunch of URLs that start with http://www.mozilla.org/ in the URL bar
so that typing www.moz in the URL bar populates the autocomplete
 5. move the mouse pointer a line or two of text below the URL bar
 6. press Ctrl-L to focus the URL bar, and backspace to clear it
 7. type (quickly) "www.mozilla.org"

Actual results (of step 7):
 * autocomplete popup generally is not visible, although the browser window
flashes to un-focused state (different color titlebar) a few times
 * the URL bar displays the URL with some missing characters, e.g., www.mzila.org

Expected results (of step 7), which are what happens when the mouse is farther
down in the browser window:
 * autocomplete popup is visible while typing URL
 * keystrokes should not be skipped

Tested in:
 * GTK2 Firefox trunk, my own build from a few days ago

I'm not sure if this is a GTK widget problem, a toolkit problem, or an
autocomplete problem, but I tend to suspect earlier in the list rather than later.

Comment 1

[Elijah Newren]

I agree, this was an utterly annoying bug.  Fixed now, though, in metacity>=2.16.3.  See http://bugzilla.gnome.org/show_bug.cgi?id=357695 for the gory details; it wasn't a mozilla bug.  (It's either a subtle definition-of-mouse-focus bug in the WM, or an X design bug; I fixed it as the former)

I don't have perms to close this, so someone else will need to.

Comment 2

[Elijah Newren]

BTW: If you run into another WM exhibiting this bug and would like to work around it, it's basically a race between when mozilla grabs the mouse (and keyboard) and when it maps the override redirect autocompletion window.  If mozilla were to grab first and then map, this bug would not be able to be triggered because the window manager wouldn't get the LeaveNotify event for the mouse leaving the main Mozilla window.