© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Since key handling inside/outside plugin objects is a delicate matter, it hasn't been solved in the first 333 comments. People could discuss it forever. But It seems to me that most annoyances are related to something on the edge of this key handling - things that can be solved by workarounds, without solving the hard task!
Here come three related problems and their workarounds:
1. When scrolling, it stops when cursor happens to be over a YouTube video.
Solution:
Never pass scroll events to a non-focused plugin object.
2. When cycling between tabs with Ctrl-Tab, I end up stuck in a plugin object.
Solution:
When showing another tab, never give back focus to a plugin object.
3. When a plugin object is full-page, I don't know where to click to de-focus.
Solution:
Take away the focus from the plugin object if I click the tab at the top. The tab was a "safe place" until a version some months ago, when the tabs could no longer be focused themselves. Nowadays a click on the tab doesn't take away the focus from a plugin object.
Should be fairly easy & effective compared to solving the complete issue!
No need for user-defined disallowed keys, negotiating with Adobe & other browser makers about standard behaviour conformance, etc. Just do IT.
PS:
I agree with the recent comments above... I never expected that MSIE would handle this issue well, but I realized that quite recently when turning to MSIE to watch a Flash movie without halts... the assumed memory corruption of Bug 490122 makes Firefox unable to show video properly after some hours of use. Ending up with MSIE handling both the video bit and the general UI handling fine while Firefox performed ridiculously in both respects was not what I was looking forward to. Something must be done quick.