1211779 - search on new tab waits for all suggestions to be completed before performing the search

Status: RESOLVED DUPLICATE of bug 1187606

(Firefox :: New Tab Page, defect)

Description

[:glob ✱]

Attachment: new-tab-search.gif

nightly 44.0a1 (2015-10-05) (no addons)

steps to reproduce:
1. move to perth, australia (or any other location that has high latency to the US)
2. open a new tab and type a longish string into its search field
3. hit enter as soon as you've finished typing

expected results:
- search performed immediately

actual results:
- there's a long delay before the search is before


looking at the browser console shows what's happening:  each character triggers an xhr request to https://www.google.com/complete/search.  the search isn't submitted until all of these requests have completed.

it looks like:

(types a search query and hits return)

> GET XHR https://www.google.com/complete/search [HTTP/2.0 200 OK 288ms]
> GET XHR https://www.google.com/complete/search [HTTP/2.0 200 OK 280ms]
> GET XHR https://www.google.com/complete/search [HTTP/2.0 200 OK 276ms]
> GET XHR https://www.google.com/complete/search [HTTP/2.0 200 OK 277ms]
> GET XHR https://www.google.com/complete/search [HTTP/2.0 200 OK 274ms]
> GET XHR https://www.google.com/complete/search [HTTP/2.0 200 OK 286ms]
> GET XHR https://www.google.com/complete/search [HTTP/2.0 200 OK 284ms]
> GET XHR https://www.google.com/complete/search [HTTP/2.0 200 OK 274ms]
> GET XHR https://www.google.com/complete/search [HTTP/2.0 200 OK 279ms]
> GET XHR https://www.google.com/complete/search [HTTP/2.0 200 OK 270ms]
> GET XHR https://www.google.com/complete/search [HTTP/2.0 200 OK 274ms]
> GET XHR https://www.google.com/complete/search [HTTP/2.0 200 OK 269ms]
> GET XHR https://www.google.com/complete/search [HTTP/2.0 200 OK 271ms]
> GET XHR https://www.google.com/complete/search [HTTP/2.0 200 OK 274ms]
> GET XHR https://www.google.com/complete/search [HTTP/2.0 200 OK 272ms]
> GET XHR https://www.google.com/complete/search [HTTP/2.0 200 OK 270ms]
> GET XHR https://www.google.com/complete/search [HTTP/2.0 200 OK 274ms]
> GET XHR https://www.google.com/complete/search [HTTP/2.0 200 OK 275ms]
> GET https://www.google.com/search [HTTP/2.0 302 Found 261ms]
> GET https://www.google.com.au/search [HTTP/2.0 200 OK 1551ms]

that's a 5 second delay between pressing return and the search _starting_.

see attached gif for a demo; compare the timing difference between the new-tab's search and google's.