Opening an incognito window doesn't automatically select it as the active window in focus
Categories
(Firefox :: Shell Integration, defect)
Tracking
()
People
(Reporter: linus.b.hoeller, Unassigned, NeedInfo)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Firefox/91.0
Steps to reproduce:
Right click firefox on task bar, click on "new private window"
Actual results:
Window opens but isn't selected as the active window, even though the cursor blinks in the navigation bar & the nav bar is selected. The window opens in the foreground but is not selected as the active window. You have to click into the window first in order to be able to type, etc.
Expected results:
Window should be automatically selected as active/in focus window when opening
|
||
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::DOM: UI Events & Focus Handling' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
|
Reporter | |
Updated•3 years ago
|
|
||
Comment 2•3 years ago
|
||
I can't reproduce this, but this component is probably better:
|
||
Comment 3•3 years ago
|
||
Seems like more of a shell integration bug -- the urlbar appears focused but the window is not active.
Hi linus
Im unable to reproduce this, I'm on windows10 64 bit and i have firefox release 91.0.2 running.
On the windows 10 task bar i right click on the firefox icon and i select "new private window" and the private window opens and im able to type and go to any site.
should i be doing something else?
-
Does this issue occur with a fresh profile? you can find the steps here: https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles?redirectlocale=en-US&redirectslug=Managing-profiles#w_starting-the-profile-manager
-
Does this issue occur in the latest nightly version of firefox? Here is a link from where you can download it: https://www.mozilla.org/en-US/firefox/channel/desktop/
please let us know
thanks
I'm marking this as Resolved-Incomplete due to lack of response. If the issue is still reproducible with the latest Firefox version, feel free to reopen the bug with more information.
Description
•