User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.76 Safari/537.36 Steps to reproduce: Open a second Firefox window, with tabs, etc. Use both the first and the second firefox window for some time. Actual results: After a while (hours) typing in the first window does not work any more. But what you type it is written in the second window. And not just typing text, but pressing the Alt key too. It makes the first window do nothing, but it shows the top menu on the second window (the one with Files, Edit, View, Help) Expected results: Typing in the first window should display that text in the first window, and typing in the second window should display that text in the second window.
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0 I observed similar behavior, except this behavior appears on the order of minutes (~5). Both typing and pressing Alt only happen in the first window, even when the second is in focus. Clicks on non-text boxes in the second window work as expected. The standard cursor becomes a text cursor appears when hovering over a text box on the second window, but clicking does not give focus to the text box.
Hi Marius, Considering this takes lot of time to reproduce, could you check, please, if this is still reproducing on latest Firefox versions? Firefox 43 can be instaled from https://www.mozilla.org/en-US/firefox/new/ and Firefox 46 Nightly from https://nightly.mozilla.org/.
User Agent Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:43.0) Gecko/20100101 Firefox/43.0 Build ID 20151210084841 Ronakbuch, Could you also, check if what you reported in Comment 1 is still reproducing on latest Firefox versions (Firefox 43, Firefox 46 Nightly)? I didn't manage to reproduce the issue on Firefox 43. If you can reproduce please provide more detailed steps on how exactly to reproduce.
Hello, I will test it and let you know. Marius
Closing this as incomplete due to inactivity and lack of response from the reporter. Feel free to reopen the bug if the issue still reproduces on a current build.