Filled based on https://bugzilla.mozilla.org/show_bug.cgi?id=997970#c10 Reproducible on: Firefox 32 beta 2 (20140728123914): Mozilla/5.0 (Windows NT 6.1; WOW64; rv:32.0) Gecko/20100101 Firefox/32.0 latest Aurora 33.0a2 (20140730004005): Mozilla/5.0 (Windows NT 6.1; WOW64; rv:33.0) Gecko/20100101 Firefox/33.0 latest Nightly 34.0a1 (20140730030201): Mozilla/5.0 (Windows NT 6.1; WOW64; rv:34.0) Gecko/20100101 Firefox/34.0 Steps to reproduce: 1. Enter different searches in search bar having Google or Amazon as default search engine 2. Pay attention to the suggestions Actual results: Suggestions are not shown all the time, sometimes space " " must be entered. If typing fast, suggestions doesn't appear. Expected results: The suggestions are shown all the time Notes: The issue reproduces also on Mac OSX 10.9.4 and Ubuntu 12.10 32-bit Will investigate to see if it's a regression or not.

(In reply to Petruta Rasa [QA] [:petruta] from comment #0) > latest Nightly 34.0a1 (20140730030201): > Mozilla/5.0 (Windows NT 6.1; WOW64; rv:34.0) Gecko/20100101 Firefox/34.0 FYI: Bug 1007979 just changed the behaviour for the nightly after this one so it would be interesting to see if this problem got better or worse tomorrow.

If you monitor the network panel while typing, do you see requests being made to the search engine as you type? What are the response times for the responses? The search service rejects responses that take longer than 500ms to arrive, if you have a high-latency connection to the search engines then you might see behavior like this. (bug 1007979 changed this code but as far as I know attempted to maintain the same behavior as before WRT request timeouts.)

Using 20140730030201 Nightly 34.0a1, the requests are visible in Browser Toolbox / Network while typing. The highest response time for Amazon was 369 ms and for Google it didn't passed 200 ms. Will test with 2014-07-31 Nightly when available.

With 34.0a1 Nightly 20140804030205 I've got the same response time, but now the suggestions are displayed all the time; it appears that bug 1007979 solved this too. Marking as RWFM, thanks all for help.