Issue 3087: Omnibox dropdown behaves poorly if users race the first async
update
http://code.google.com/p/chromium/issues/detail?id=3087
New issue report by [EMAIL PROTECTED]:
If the omnibox popup is open, and another query starts, and then a user
hits down or clicks a result, we get into a weird state where the popup is
showing results that don't match what's on the controller (this is as of
after a refactoring patch I'll land soon).
sky and I came up with the following crazy hack:
* Add yet another AutocompleteResult to the controller, holding the
previous result set until the first RESULT_UPDATED notification fires, at
which point it's updated in sync with result_; when the popup closes we
clear this result set.
* Add a saved text/selection to the edit model. This gets cleared when a
RESULT_UPDATED notification fires or the popup closes. It is set in
OnBeforePossibleChange only if it is currently clear.
* If the user uses mouse or arrows to interact with the popup while the
results are desynced, stop the query, copy the the saved results over to
the main results, and notify RESULTS_ROLLED_BACK or similar. The popup
does nothing on receiving this; the edit resets itself to its saved data
and clears the saved data.
Issue attributes:
Status: Assigned
Owner: [EMAIL PROTECTED]
Labels: Type-Bug Pri-2 OS-All Area-BrowserUI
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Chromium-bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/chromium-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---
