© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Our product is a full page web application which renders in Flash, and in that context the user expects our application to capture shortcut keys (we have customer authored bugs to prove it). Since we're a full page web application, it doesn't make sense for the web browser to capture shortcut keys, and we'd like to handle those key presses to create a more user friendly experience for our customers.
Just my $.02, but I feel that the solution S. Ali Tokmen describes is both elegant, and ideal.
By giving the plugin application the ability to handle the event, you give the plugin developer the power to do the right thing. Otherwise, the plugin developer's hands are tide and they are unable to do the right thing for the user.
It would seem to me that everyone wins, assuming the default behavior is that the browser handles the key events that aren't explicitly handled by the plugin.