Status: Available Owner: ---- Labels: Type-Bug Pri-2 OS-All Area-BrowserUI Size-Small Mstone-2.1 Fixit
New issue 9734 by [email protected]: Remove space as a tab-to-search trigger http://code.google.com/p/chromium/issues/detail?id=9734 Presently, we use space as a secondary (hidden) trigger for tab-to-search. Problem: We've had reports that we end up triggering tab-to-search inadvertedly for generic searches when a keyword is imported from another browser: 1. Other browser has keyword defined "google". This keyword likely wasn't created by the user, but rather by the browser vendor or distributor. 2. User installs Chrome and imports settings from existing browser. 3. User types "google news" into the address bar to search for the "Google News" service. While the user types, the omnibox morphs into TTS mode, which is visually jarring because it's a rather major unexpected change in the text field. (When invoked via Tab, it's typically expected). The option to search for "google news" is the second item in the dropdown, but if you're a typical user who doesn't look in the dropdown, and never created the mysterious keyword that's triggering TTS, you're going to be puzzled why you can't just type it in. This problem impacts Chrome users more heavily because of the combined search and address bar. In our attempt to mimic other browser's somewhat obscure space-invoked keyword system, we've made the omnibox act less like a conventional search bar. This seems like the wrong tradeoff. Proposed solution: At the design fixit, we decided the best thing to do would be to try disabling the space key as a trigger for TTS. We heavily upsell Tab directly in the address bar and TTS is automatic, so the Chrome system should be more intuitive. Space exists only as a compatibility mode for browsers that don't combine search and navigation bars. Another alternative would be to not import keywords from other browsers, but we found this less desirable because we'd skip ones that users had deliberately created. -- 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 -~----------~----~----~----~------~----~------~--~---
