Open Bug 1459560 Opened 2 years ago Updated 2 years ago
[OOP] Browser content frame focus not restored after closing page or browser action
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0 Build ID: 20180430165945 Steps to reproduce: On Linux (Ubuntu 16.04.4) with Firefox 61a2: 1. Open Firefox 2. Navigate to about:debugging and load the minimal example add on which is attached to this report 3. Navigate to google.com and focus the search field 4. Open the add on browser action 5. Observe that the input field in the browser action is focused and press some keys to verify 6. Close the browser action by pressing escape Actual results: After closing the browser action no UI or content element has visible focus. Pressing Tab moves focus to the Tab bar, specifically the currently visible tab. Expected results: Focus should be restored to the google.com search field. This is also the resulting state when executing steps 1 - 6 on Windows.
I've been following bug 1324255 which fixes the focus transition occurring between steps 3 and 4, but rather than bringing this up in a comment for that bug, I've decided to report it as a new issue as the Windows build does not seem affected.
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:62.0) Gecko/20100101 Firefox/62.0 Build ID: 20180509220105 Hi gesimu, I managed to reproduce the issue as described on the latest Nightly 62.0a1 (20180509220105/2018-05-09) and Firefox Beta 61.0b3 on Ubuntu 16.04 x64.
This seems to be a regression. I can reproduce the issue with my own add-on with FF 60.0, while it used to work with FF 59.0.3 (both times using Ubuntu 16.04). Also, bug 1435687 seems to be related?
From my testing, both osx and windows is fine. Linux works if I turn on remote extensions.
Summary: Browser content frame focus not restored after closing page or browser action → [OOP] Browser content frame focus not restored after closing page or browser action
I can confirm that setting extensions.webextensions.remote to true results in the expected behavior on Linux.
You need to log in before you can comment on or make changes to this bug.