Open Bug 1332944 Opened 4 years ago Updated 2 years ago

Delay for omnibox.onInputChanged suggestions increases with text length


(WebExtensions :: Frontend, defect, P3)



(Not tracked)


(Reporter: Fallen, Unassigned)


(Blocks 1 open bug)


(Whiteboard: omnibox, investigate, triaged)


(1 file)

Using the following snippet:

browser.omnibox.onInputChanged.addListener((text, suggest) => {
    content: "foo",
    description: "bar"
    content: "baz",
    description: "quux"

should be fast enough that results will be displayed instantly. I've made the following observations:

1) Entering 1-3 characters after the keyword is pretty much instant, but it flickers between typing characters because the item is removed and added again. Ideally the item should be re-used, so no flickering occurs

2) When entering 4 or more characters, there is a noticeable delay between typing the character and the items appearing. The more characters, the longer it takes.
Assignee: nobody → mwein
Priority: -- → P1
Whiteboard: omnibox, investigate
Could you confirm whether the suggestions appear for the most part instantly after you stop typing? I suspect that the delay is due to the Awesome Bar waiting for the user to finish inputting text before processing it.
Flags: needinfo?(philipp)
Attached video Screencast - v1
Other awesomebar results appear instantly, there is a delay only for the omnibox results. See attached screencast with me entering "amo cliqz". Full add-on code at if you can't reproduce using the snippet.
Flags: needinfo?(philipp)
Whiteboard: omnibox, investigate → omnibox, investigate, triaged
This is unscientific, but I think this might not strictly be an omnibox bug. While testing my WebExtension, I'm seeing several seconds of lag in my usual profile, with its other extensions, large pile of history, open tabs, etc--but I *don't* see lag in a fresh profile: long inputs get shown quickly.
This is an assigned P1 bug without activity in two weeks. 

If you intend to continue working on this bug for the current release/iteration/sprint, remove the 'stale-bug' keyword.

Otherwise we'll reset the priority of the bug back to '--' on Monday, August 28th.
Keywords: stale-bug
Assignee: matthewjwein → nobody
Keywords: stale-bug
Priority: P1 → P2
Priority: P2 → P3
Product: Toolkit → WebExtensions
You need to log in before you can comment on or make changes to this bug.