Bryan Ischo Reporter
	Description • 8 years ago

User Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0
Build ID: 20160321091910

Steps to reproduce:

1. Start Firefox.
2. Open a new window using any method (menu bar or ctrl-N)
3. Switch back to previous window



Actual results:

After switching back to the previous window, keyboard input events were still sent to the new window.  There is no way to get any window aside from the most recently created window to gain keyboard input focus.  All key events always go to the most recently opened window regardless of which window has focus.

Also, I noticed that when I use the menu to open the preferences page from any window other than the most newly created window, that page opens in the most newly created window instead of the window that I used to open the preferences page.


Expected results:

I should be able to select any window and type into it.

PLEASE NOTE: This issue is reproducible with the TWM window manager.  I do not know if it is reproducible with any other window manager.

	Bryan Ischo Reporter
	Comment 1 • 8 years ago

Hm.  I am using this link:

https://ftp.mozilla.org/pub/firefox/releases/

to try out different versions of firefox in an attempt to find the one in which this bug was introduced.

I have found that the following versions DO NOT experience this bug:

44.0b9
45.0b9
46.0b6

I am using Fedora Linux version 24, and firefox reports its version in the "About Firefox" dialog as 45.0.1.  I will try to test with that exact version, but this is starting to feel like a problem specific to Fedora Linux.

	Bryan Ischo Reporter
	Comment 2 • 8 years ago

OK so I tried the 45.0.1 version that is available from ftp.mozilla.org, and even it works without this bug.  So this must be a problem introduced by Fedora Linux in some way or other.  I will continue to investigate.

	Martin Stránský [:stransky] (ni? me)
	Comment 3 • 8 years ago

I believe this is a widget bug introduced by Gtk3.20 in Fedora 24.

	Martin Stránský [:stransky] (ni? me)
	Comment 4 • 8 years ago

Confirmed, I see that on Fedora Firefox build, my own trunk without any patches (but build for gtk3) does not expose that.

	Martin Stránský [:stransky] (ni? me)
	Comment 5 • 8 years ago

btw. It sometimes happens in other DE (MATE for instance) but it's 100% reproducible under TWM.

	Martin Stránský [:stransky] (ni? me)
	Comment 6 • 8 years ago

This is actually the bug with XINPUT2 enabled in gtk3. Mozilla disables because of this issues, but it's enabled in Fedora. The XINPUT2 bugs are hard to reproduce in GNOME/MATE, but can be 100% reproduced in TWM. So we have a chance to fix that and enable XINPUT2 again for all DE.

	Karl Tomlinson (:karlt)
	Comment 8 • 8 years ago

Perhaps this is not the same bug as bug 1196777.
Which GTK versions are known to demonstrate this bug?

Could it be a regression from
https://git.gnome.org/browse/gtk%2B/commit/?id=d55b815