Closed Bug 1204326 Opened 10 years ago Closed 5 years ago

Location bar loses keyboard focus, autocomplete, enter-to-go, etc.

Categories

(Firefox :: Address Bar, defect, P5)

41 Branch
x86_64
Linux
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox43 --- affected

People

(Reporter: dustin, Unassigned)

Details

STR: 1. ctrl-t to open new tab 2. type search query 3. hit enter Expected Results: a. after step 1, see blinking insertion cursor in location bar b. after step 2, see autocomplete dropdown c. after step 3, search occurs with configured search engine Actual Results: a. no cursor b. no autocomplete c. nothing happens (43.0a1 (2015-09-12))
Sorry, I cannot reproduce. Could you please check with Safe mode if any add-on is conflicting with the location bar code?
I should have added to the STR `0. be in some condition I haven't identified yet` I'll keep working on finding out what that condition is.
This seems to start
Assignee: nobody → dustin
Sorry for the half-comment there. I was just able to reproduce in safe mode. I had https://github.com/buildbot/buildbot/blob/master/master/setup.py#L37 open, hit ctrl-t, and proceeded with the STR from comment 0.
Assignee: dustin → nobody
(Firefox 41.0.1)
Version: 43 Branch → 41 Branch
firefox 43 has lots of changes in the location bar code, I wonder if it will make a difference. so far I am unable to reproduce the bug
I originally saw this in 43 (I was running nightly at the time; comment 0) and then reproduced it in safe mode with release, hence the version change in comment 5. It took me two days of using 41 in safe mode to reproduce the problem, so it is fairly rare, and I have not been able to isolate any particular conditions that make it more likely. I have a hunch that it has to do with leaving a page that uses flash, but since most pages use flash, and since flash generally eats ctrl-t when it steals keyboard focus, I haven't been able to support that hunch with data.
Ah! This has to do with window focus. Revised STR: 1. create a new window (ctrl-n) 2. click on the old window 3. ctrl-t, ctrl-l 4. start typing I'm using a tiling wm (i3). A few observations: this seems to occur with all text-entry boxes. For example, right now I'm typing this comment without a visible text cursor. Just shifting to the other window and back is enough to trigger this (no need to actually create it). The window gets highlighted as if it is the foreground window, but no text cursor. Switching windows by clicking on them or by using keyboard shortcuts will both produce this behavior.
Priority: -- → P5

Can't reproduce in Nightly 84.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.