Updates:
Summary: Omnibox does not support [ctrl-]shift-enter
Status: WontFix
Comment #7 on issue 791 by [email protected]: Omnibox does not support
[ctrl-]shift-enter
http://code.google.com/p/chromium/issues/detail?id=791
No, this is WontFix Working As Intended.
The incentive to use these is low -- only Firefox supports them, they're
cumbersome
to trigger, and net/org usage is far lower than com.
However, if the cost to supporting them were also low, we'd go ahead and do
it. And
in fact we implemented it once upon a time. Unfortunately, there are two
negative
side-effects:
* Because triggering these redraws things in the popup, and reorders
results, hitting
shift results in much more visual flicker. This was incredibly
distracting. Firefox
does not suffer from this since its dropdown contains only suggestions, not
also
"what's going to happen when you hit enter".
* Users trying to type search queries began tripping over wrong-URL pages
when they
had the shift key down when hitting enter. Firefox suffers less from this
since
users don't generally type things that don't look like URLs already into
the address
bar.
The second issue was addressed to some degree via heuristics that ignore
the modifier
if the user has pressed another key since depressing it. However, the
first issue,
which hasn't changed, was the primary reason we figured the cost of these
was greater
than their low utility.
--
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
-~----------~----~----~----~------~----~------~--~---
