Firefox sometimes doesn't start with cursor focused on address bar
Categories
(Firefox :: Address Bar, defect, P3)
Tracking
()
People
(Reporter: marcos_d2, Unassigned)
References
Details
(Keywords: papercut, Whiteboard: [fxsearch])
Attachments
(1 file)
48.02 KB,
image/png
|
Details |
Comment 1•9 years ago
|
||
Updated•9 years ago
|
Updated•8 years ago
|
This issue still occurs with 81.0.1 (64 bits) on Windows 10 Pro 64 bits (version 2004, build 19041.508).
I confirm that it affects the taskbar's jumplist. Opening a new window with the Firefox menu button or using the keyboard shortcuts does not trigger the focus issue.
As a workaround, it just occurred to me that we could "simply" disable the focus on the address bar when opening up the window from the jump list. This could give the user a hint that the window is not ready to receive keyboard input.
Comment 10•5 years ago
|
||
Confirming bug - Windows 10 Pro Version 1909 (OS Build 18363.1256)
With Firefox closed:
Right click Firefox taskbar icon, click Firefox - cursor focuses to address bar
Right click Firefox taskbar icon, click New private Window - cursor not focused on FF although cursor blinks within address bar. Ctrl>L will not allow typing in address bar. Workaround: use Alt Shift Tab (Firefox Incognito opens as the last icon) to focus on FF.
Comment 11•4 years ago
|
||
I can confirm.
If I right click Firefox in the taskbar on Windows, and click "Open new tab," "Open New Window," or "New private window," this bug happens. (It does not matter if Firefox is open already or if this is the first window being opened -- the result is the same.)
The address bar is visibly focused, with a flashing cursor. But nothing I type shows up in the address bar.
Comment 12•4 years ago
|
||
Something else strange happens: No keyboard shortcuts work in this bug's triggered state. (Shortcuts I tried: as Ctrl + W, Ctrl + Q, Ctrl + H...)
I think Firefox may be swallowing up all keyboard input, during this bug.
Comment 14•4 years ago
|
||
There are two different problems described here. The reporter says says the address bar is not focused when it should be, but recent comments say it appears focused when it isn't actually. Maybe these are two descriptions of the same thing, depending on your definition of focused? It's hard to say without knowing whether the address bar was drawn with a focus ring when the reporter filed the bug.
Bug 1745684 is clearly about the second problem, where the address bar has a focus ring and therefore appears to be focused, but the window is not actually focused/active so nothing happens when you try to type into it.
Comment 15•3 years ago
|
||
The steps to reproduce are the same as bug 1745684, so it makes sense to keep that one that is in the right component.
Description
•