On Aug 23, 3:18 am, Evan Martin <[email protected]> wrote: > It's already the case that if a page grabs a key it overrides the > Chrome shortcut, so this would actually work properly with no > additional effort.
In that case, the issue is that the menu shortcuts won't work reliably, which (1) can get quite frustrating because you never really know what a shortcut will do and (2) leads to the menus or other core functionality remaining inaccessible in case of a clash. Unfortunately for people relying (or even having to rely) on the keyboard, most browsers get this wrong. The solution I had envisioned for Firefox was to clearly separate chrome and content shortcuts depending on the modifier: Alt+Shift +<key> only for content and Alt+<key> and Ctrl+(Shift+)<key> only for chrome. At least the first part has been implemented in Firefox 2.0. For Chrome, being mostly about content, we could easily concede Alt +<key> to content and instead use a different modifier for accessing the menu buttons (since they're not real menus anyway, the platform consistency argument doesn't necessarily trump other arguments) such as Alt+Shift+<key> which we already use for accessing the toolbars. The Ctrl+<key> shortcuts should however remain restricted to Chrome, so that webpages can't e.g. prevent you from closing a tab with Ctrl+W (not sure how somebody without a mouse could currently get away from such a webpage at all). --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
