Calling setDefaultSuggestion within onInputChanged should update the default suggestion for the current search query
Categories
(WebExtensions :: Frontend, defect, P3)
Tracking
(Not tracked)
People
(Reporter: Fallen, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: omnibox, triaged)
Attachments
(1 file)
50.15 KB,
image/png
|
Details |
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".
Reporter | ||
Comment 1•7 years ago
|
||
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•7 years ago
|
||
test how it works on chrome - to validate desired behavior.
Comment 3•7 years ago
|
||
Confirmed bug.
Updated•7 years ago
|
Updated•7 years ago
|
Updated•7 years ago
|
Updated•7 years ago
|
Comment 4•7 years ago
|
||
JFTR, Chromium has the desired instant-update behaviour.
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•7 years ago
|
Updated•7 years ago
|
Comment 7•6 years 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•6 years ago
|
Comment 8•6 years 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.
Comment 9•3 years ago
|
||
I encountered this as well (https://github.com/huhu/rust-search-extension/issues/98). Is there a way for the extension to work around the problem?
Comment 10•3 years ago
|
||
This bug is extremely confusing when trying to use omnibox.setDefaultSuggestion
to explain the choice of suggestions available. It shows the explanation of the previous set of suggestions, not the ones currently being displayed below it. This makes omnibox.setDefaultSuggestion
worse than useless in these circumstances, in that it misleads the users rather than helping them.
This bug was reported 5 years ago and downgraded from P2 to P3 4 years ago. What is the timescale for fixing it please?
Is there a workaround in the meantime?
Updated•2 years ago
|
Comment 11•5 months ago
|
||
This bug is still there and super confusing for all users who use omnibox search. Please finally fix this!
Description
•