Comment 436 for bug 263435
Revision history for this message
|
|
#436 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Plugin ability to receive keys should be limited so it does not interfere with, or disable the functionality of the host application (browser).
That should be the main concern for everyone who ever tries to fix this bug, regardless of the way they intend to do that. If you want to push for an API, then by all means do it, but _we need an interim fix_ that will enable us to escape the plugin wrath *NOW*.
What I suggest is that at least the following key combinations:
- Alt+D
- Alt+F4
- Ctrl+Tab
- Ctrl+T
- Ctrl+W/Ctrl+F4
Be reserved for the browser with no way for plugins to override them.
For the last 10 years, basic browser functionality of page and tab navigation is broken when there is a plugin on a page.
Only after someone makes a patch with those keys working properly when there is a plugin on the page, and after end users can download it, only then it will make sense to continue debating and perhaps working on a better solution.
It is very bad to do nothing because you cannot find a way to please everyone.
Finally, let me remind you that developers of web applications and "visionaries" who are pushing for web-centric development are a minority when compared to the number of people using the browser -- they should not be the ones to decide what is best for the rest of us.