Sounds like a reasonable feature request. Please file it at http://new.crbug.com .
However, it is very unlikely this is going to happen for 4.0. Nico On Mon, Jan 11, 2010 at 8:55 AM, langdon <[email protected]> wrote: > Hopefully this is the right forum to propose an issue I have with > Chrome... It doesn't seem like a lot of thought has been given to the > shortcut keys assigned to various menus and context menus within > Chrome. The biggest offender is the context menu for each tab. In > most every other browser that supports tabs, I can right click a tab, > press the C key, and my tab will be closed. However because no > shortcut is defined, I either have to click the menu item or press > ENTER after pressing C. > > You may be wondering why I care enough to post here about it. My > mouse accuracy is terrible, so I personally find right clicking a huge > target and pressing a key (a key close to where my left hand is > already sitting) suits me better. I find it also better (since 1 hand > is generally already on the mouse when browsing the web) than shifting > my hand position to use CTRL+W. > > Here are my suggestions for changes: > > File: > - He&lp or Hel&p (currently it conflicts with Extensions -- there's > no shortcut to even get to extensions currently, "ALT+F, E" would be a > great one) > > Window Context: > - T&ask Manager (it conflicts with new tab) > > Tab Context: > - New &tab > - &Reload > - &Duplicate > - Pin t&ab (as opposed to &Pin tab for good left hand use) > - &Close tab (!) > - Clo&se other tabs > - Close tabs to the ri&ght (not sure if this really needs one) > - Close tabs opened by t&his tab (alternatively "&opened" -- not sure > if this really needs one) > - R&eopen closed tabs (fine as is, odd that it's the only one with a > shortcut defined) > - &Bookmark all tabs... > > Some may argue that this is really not that important, but I feel > strongly that this type of attention to detail to be very important in > user interface design. What's the most effective route I can take to > have this resolved by the final 4.0 build? Seems that ti would take > someone 5 minutes to fix it (I'd be happy to if I knew how to get at > the Chrome source and make commits). > > Cheers, > Langdon > > -- > Chromium Discussion mailing list: [email protected] > View archives, change email options, or unsubscribe: > http://groups.google.com/group/chromium-discuss >
-- Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss
