I'm not sure I understand all this email, but I'll take a shot at it. On Thu, Dec 18, 2008 at 6:09 AM, Simon B. <simon.boh...@gmail.com> wrote:
> Maybe row-numbering the suggestions also for real, in the browser, > could help somehow? I could maybe type skä.3 <enter> (.3 is not a TLD, > and maybe uncommon enough to be prevented from searching for it?) Pretty undiscoverable, and scanning for the row number, figuring out which one it is, and typing "." + it is almost as many keystorkes, plus much slower and more mental overhead, than simply arrowing to the item. Row 2 "skä/" only appears as long as there is only one word (=possibly > valid domain name). We could hide row 2 if parallell lookup in dns+ > (incremental) search in browser history says that domain doesn't > exist, forcing the user to do a search for it -- often a good idea in > those cases! DNS and history search both take arbitrarily long times. We can't rip an item out of the list after it's been there for an arbitrary length of time (we already have an effect somewhat like this when incremental results come in scored higher than existing results and bump them off the list bottom). Plus DNS lookup can't properly tell you whether a hostname is reachable; only attempting to open it can do that. I do have some ideas on how to improve scoring here so that this entry will fall somewhat further down the list and let other, better suggestions rise above it. (Row 2, i.e. "foo/" even stays visible with one word + space, which > seems like an oversight!? crbug.com/5664). Not an oversight. I'm also curious whether there is need for one suggestions-row for the > default search, since I get that with enter, or clicking the Go > button. This touches on a very subtle design point. The dropdown is NOT a list of "possible alternates to what you're typing in" like it is in other browsers. The dropdown is the complete list of all choices we allow you to have for this input. Because searching for your input is a choice, it's in the list; if it's the default action, then it will be selected too. This leads to invariants like: * The dropdown will always be open during user editing (unless you've closed it by clicking somewhere else, in which case it will reopen as soon as you begin editing again) * The dropdown always has exactly one selection * The selection always describes what will happen when you press enter This increases stability/predictability of outcome. If we didn't show you an entry for your default action, then how would you know whether the browser would search or navigate for a single word that might be an intranet site? There are possible modifications here, like iconography inside the edit control itself instead of a selected row in the dropdown, or popping the dropdown back open immediately if you refocus the edit control while in the midst of editing, but I'm not sure either one would be a win. PK --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to chromium-dev@googlegroups.com To unsubscribe from this group, send email to chromium-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
