© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Comment #316 sounds good to me.
More opinion/solution for a compromise that minimizes both browser annoyance and plug-in functionality loss:
When working inside a browser, you can't expect to do whatever you want. You have to conform to what is accepted and appropriate. (Just like when working in a kindergarten, church, hospital, etc. Nothing strange with that.) A Flash programmer that rely on being served every key/mouse event in the world will not be successful. The browser should get whatever events that it wants to use, even if the plug-in has focus. Everything else is (apparently, just look at this discussion thread) very annoying for the browser user.
However, when the browser consumes the event right in front of the plug-in, a little information "flag" (perhaps similar to the little translucent "block" thingy that Adblock Plus uses if not hidden in the settings) could be shown near the plug-in for some seconds, allowing the user to click on it to grant permission for the plug-in to get all events from now on. This would make it possible for a plug-in to get practically ALL events if it really wants to - but without annoying a user who just want to cycle through the tabs, scroll the page, or close it.