Comment #9 on issue 25756 by [email protected]: Some Keyboard Shortcuts (Cmd-L) don't work when flash plugins eat them http://code.google.com/p/chromium/issues/detail?id=25756
I was involved in some of the discussion about how Gecko handles this case on the Mac. The Firefox behavior (on Mac) is to always give the main menu a chance to handle command-keys (bypassing the normal event system) if a plugin is focused, but then to go ahead and send the event to the plugin anyway (unless the event did something like close the window containing the plugin). The last bit is to handle things like Copy/Paste, where the browser can't do anything useful with them, but the plugin can. > plugins should not be treated differently than web content. The problem with that is that, as I understand it, the behave differently. A website has to go out of its way to intercept command keys, and if they do something that annoys users, users can complain--but the basic idea of allowing that is that we assume that if a website grabs a shortcut, they are going to do something with it that they think is relevant. IIRC, plugins have no way of saying "I didn't use this command, go crazy" the way sites do, so *every* plugin eats *every* shortcut, even though they probably aren't doing anything useful with them. If pages let commands through unless they specifically want them, and plugins can't possibly let commands through, making a blanket policy to cover both is probably not in the best interest of users. -- 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 -~----------~----~----~----~------~----~------~--~---
