Status: Unconfirmed Owner: ---- Labels: OS-Linux Area-Misc Size-Medium Type-Bug
New issue 21587 by [email protected]: omni search does nothing when search term is only a single character http://code.google.com/p/chromium/issues/detail?id=21587 Chrome Version : 4.0.208.0 (Developer Build 25977) OS + version : Linux version 2.6.24-gg24-generic CPU architecture (32-bit / 64-bit): x86_64 window manager : gnome URLs (if applicable) : any single character string Behavior in Firefox 3.x (if applicable): not applicable Behavior in Chrome for Windows (optional): did not test What steps will reproduce the problem? 1. Go to search box. 2. Type in a single character. 3. Press enter, observe that the browser doesn't go anywhere. (the search results do show up in the dropdown box though) What is the expected result? The browser should take the user to the search engine that they have setup. What happens instead? Didn't go anywhere. Please provide any additional information below. Attach a screenshot and backtrace if possible. I used a custom search engine set to "http://%s/"; (see first attached screenshot) to emulate firefox behavior, where the URL box takes me directly to where I tell the browser to go, instead of going to a search engine first. This is a real time saver because our company has many intranet sites with short URLs (e.g. http://b/, http://c/, http://s/, http://w/, http://www/). Using this no-op search engine setting, I don't have to type the http:// when I need to go to a new intranet site, and I don't need to wait for the search engine result page, both saves me a bit of time. As of build 25617, and also tested on build 25977, pressing enter with single character terms (see second attached screenshot) no longer actives my no-op search engine, and either I have to type the full http:// prefix, or add a trailing slash, both are a bit inefficient. It would be great if we can have the old behavior back. Attachments: search-engine-setup.png 10.6 KB press-enter-goes-nowhere.png 39.9 KB -- 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 --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
