Yea, we added ALT+E and ALT+F for opening the menus to make them accessible on Windows. (Similar to File/Edit in any Window screen menu). There was a post long time ago regarding that and everyone agreed adding that. They were added through the chrome_rc.grd file.
Now, if the shortcut key exists in the website, how would browser keyboard shortcuts (that have the same keys) act? Should the browser shortcuts be disabled once a renderer shortcut exists? - Mohamed Mansour On Thu, Nov 12, 2009 at 1:28 PM, Nico Weber <tha...@google.com> wrote: > +1 on filing a bug. Please paste a link to your bug here when you've filed > it. > > In the meantime, I think mhm added alt-e and alt-t on windows. It > sounds as if these mappings take effect before being sent to the > renderer? > > On Thu, Nov 12, 2009 at 10:09 AM, Peter Kasting <pkast...@google.com> > wrote: > > On Thu, Nov 12, 2009 at 9:14 AM, Jeff Mikels <jeffmik...@gmail.com> > wrote: > >> > >> I don't know if people consider this a problem or not, but 4.0 > >> introduced new behavior for access keys. > > > > What OS? I'm guessing Linux? (Keys are different on all OSes) > > I have no idea what guarantees browsers try to make for alt+key. I'm not > > sure that on Windows pages can even get these events, and I'm not sure > what > > the typical shortcut is for accessing named menus on Linux. > > It might be better to file a bug rather than emailing chromium-dev. > > PK > > > > -- > > Chromium Developers mailing list: chromium-dev@googlegroups.com > > View archives, change email options, or unsubscribe: > > http://groups.google.com/group/chromium-dev > -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
