Calling setDefaultSuggestion within onInputChanged should update the default suggestion for the current search query

NEW
Unassigned

Status

defect
P3
normal
2 years ago
4 months ago

People

(Reporter: Fallen, Unassigned)

Tracking

(Blocks 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: omnibox, triaged)

Attachments

(1 attachment)

Posted image Screenshot - v1 β€”
When using setDefaultSuggestion during onInputChanged to update the item text for the first suggestion item, the update is not instant.

To test, set up a WebExtension as in http://stackoverflow.com/a/17246127 where the description for setDefaultSuggestion contains the text.

See attached screenshot where I entered "foo", paused a bit, then added "bar".
Another interesting bit I just noticed, the "Search for xxx with" text seems to be an another schedule, it looks like I also paused after "fooba".

Comment 2

2 years ago
test how it works on chrome - to validate desired behavior.
Assignee: nobody → mwein
Priority: -- → P1
Whiteboard: omnibox, investigate
Confirmed bug.
Summary: Calling omnibox.setDefaultSuggestion during omnibox.onInputChanged does not update default suggestion → Calling setDefaultSuggestion within onInputChanged should update the default suggestion for the current search query
Whiteboard: omnibox, investigate → omnibox

Updated

2 years ago
Whiteboard: omnibox → omnibox, triaged
Priority: P1 → P2
webextensions: --- → ?

Updated

2 years ago
webextensions: ? → ---

Comment 4

2 years ago
JFTR, Chromium has the desired instant-update behaviour.

Comment 5

2 years ago
I have encountered this issue as well. In general it breaks the:

Search TargetSite for "...." 

pattern, in which the first suggestion is expected to update instantly when text is typed. It can also break ported Chrome extensions relying on this behavior, as well.

Updated

2 years ago
Assignee: matthewjwein → nobody

Updated

2 years ago
Duplicate of this bug: 1407385

Updated

2 years ago
Priority: P2 → P3

Comment 7

a year ago
I also would like to push this bug. WebExtension's omnibox.setDefaultSuggestion is always one keyInput behind which is very confusing if you want to give the user feedback what he is gonna searching/typing in his omnibox.

Please increase the priority of this. It breaks one essential omnibox WebExtensions feature.

Thank you guys, and greetings from Vienna,

Clemens

Updated

11 months ago
Product: Toolkit → WebExtensions

Comment 8

11 months ago
Hi,

I just received again user complaints about this bug, because it is super confusing if the update of the default user suggestion lags one keystroke behind. Please take a look at this issue. I guess it's an easy to fix bug. Thank you very much.
You need to log in before you can comment on or make changes to this bug.