Opened 8 years ago

Closed 6 years ago

#7100 closed defect (worksforme)

Firefox location bar loses focus with HTTPS Everywhere and suggestions enabled

Reported by: cypherpunks Owned by: pde
Priority: Medium Milestone:
Component: HTTPS Everywhere/EFF-HTTPS Everywhere Version: HTTPS-E 3.0.0
Severity: Keywords:
Cc: a2883-tor@… Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


While typing in the location bar with suggestions enabled (browser.urlbar.autocomplete.enabled set to true), after the first characters typed have caused some suggestions to appear, as soon as a character is typed that does not match any of the suggestions, the location bar loses focus. This problem disappears when HTTPS Everywhere is disabled and reappears when HTTPS Everywhere is enabled. (It also disappears when browser.urlbar.autocomplete.enabled is set to false, but that reduces usability of Firefox too much to be a workaround.)

The bug does not occur with every instance of Firefox, and if an instance of Firefox does not exhibit the problem, it will not exhibit it even if running for a long time. On the other hand, if an instance of Firefox has the problem, it will not disappear while that instance is running. It seems to me that the probability of getting a buggy instance of Firefox is correlated to the amount of history data available, i.e. probability is somewhat low with a fresh install of Firefox, then gradually rises as the history database fills up.

I am using Firefox 16.0.1 (and have had the problem for several releases of Firefox before that) with NoScript and AdBlock Plus installed as extensions. There are no plugins. OS is GNU/Linux using Debian 6.0.6 as base distribution.

Child Tickets

Change History (3)

comment:1 Changed 8 years ago by pde

When you say that some "instances" of Firefox exhibit this problem and others don't: is Debian 6.0.6 + Firefox 16.0.1 + NoScript + ABP a reliable way to make an instance with the problem? Which versions of NoScript and ABP to you have?

(If you can reliably make new Firefox profiles that have the bug then I think we'll be in good shape to start investigating).

comment:2 Changed 8 years ago by cypherpunks

Not reliable as in "I can guarantee that the next Firefox 'instance' (the next Firefox process started) will exhibit the problematic behaviour". Only reliable as in "when quitting and restarting Firefox, without changing anything else, I will eventually get a process that exhibits the problem". I realize this does not lend itself to stepping through code in gdb.

At the moment, I've got NoScript 2.5.7 and AdBlock Plus 2.1.2.

comment:3 Changed 6 years ago by jsha

Resolution: worksforme
Status: newclosed
Note: See TracTickets for help on using tickets.