I'm not allowed to point out how incredible it is that this bug will still be unsolved in Firefox 4, so instead I am filing four enhancement requests suggesting efficient workarounds for the most annoying results of this bug: (Three of them were proposed already a year ago in my Comment 333 above)
1.
Problem:
When scrolling, it stops when cursor happens to be over a YouTube video.
Solution:
Never pass scroll events to a non-focused plugin object.
[ Bug 625805 - Keyboard command enhancement: save lost scroll events (workaround for Bug 78414) ]
2.
Problem:
When cycling between tabs with Ctrl-Tab, I suddenly end up stuck in a focused plugin object.
Solution:
When showing another tab, never give back focus to a plugin object.
[ Bug 625806 - Keyboard command enhancement: keep tab navigation (workaround for Bug 78414) ]
3.
Problem:
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.
[ Bug 625808 - Keyboard command enhancement: safe click zones (workaround for Bug 78414) ]
0.
Problem:
Shortcut keys are not working for Firefox functions, they end up in the plug-in. But is anybody using them in the plug-in? Probably not nearly as often as someone is annoyed by Firefox's lack of function. And good plug-in programmers would never use these browser-common shortcuts anyway (apart from in malware), so why keep them in the plug-in?
Solution:
Never give the most important shortcuts F11, Ctrl-T, Ctrl-W, Ctrl-Tab, Ctrl-Shift-Tab, Ctrl-PgUp, and Ctrl-PgDn to a plug-in. Keep their Firefox functionality instead. *IF* users have problems with these shortcuts not working in a plug-in anymore, they will report it in this bug report system. If no reports are coming - then there was no use passing the keys to the plug-in!
[ Bug 625809 - Keyboard command enhancement: reclaim Firefox functionality (workaround for Bug 78414) ]
Please include these enhancement in Firefox 4.
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.
I'm not allowed to point out how incredible it is that this bug will still be unsolved in Firefox 4, so instead I am filing four enhancement requests suggesting efficient workarounds for the most annoying results of this bug: (Three of them were proposed already a year ago in my Comment 333 above)
1.
Problem:
When scrolling, it stops when cursor happens to be over a YouTube video.
Solution:
Never pass scroll events to a non-focused plugin object.
[ Bug 625805 - Keyboard command enhancement: save lost scroll events (workaround for Bug 78414) ]
2.
Problem:
When cycling between tabs with Ctrl-Tab, I suddenly end up stuck in a focused plugin object.
Solution:
When showing another tab, never give back focus to a plugin object.
[ Bug 625806 - Keyboard command enhancement: keep tab navigation (workaround for Bug 78414) ]
3.
Problem:
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.
[ Bug 625808 - Keyboard command enhancement: safe click zones (workaround for Bug 78414) ]
0.
Problem:
Shortcut keys are not working for Firefox functions, they end up in the plug-in. But is anybody using them in the plug-in? Probably not nearly as often as someone is annoyed by Firefox's lack of function. And good plug-in programmers would never use these browser-common shortcuts anyway (apart from in malware), so why keep them in the plug-in?
Solution:
Never give the most important shortcuts F11, Ctrl-T, Ctrl-W, Ctrl-Tab, Ctrl-Shift-Tab, Ctrl-PgUp, and Ctrl-PgDn to a plug-in. Keep their Firefox functionality instead. *IF* users have problems with these shortcuts not working in a plug-in anymore, they will report it in this bug report system. If no reports are coming - then there was no use passing the keys to the plug-in!
[ Bug 625809 - Keyboard command enhancement: reclaim Firefox functionality (workaround for Bug 78414) ]
Please include these enhancement in Firefox 4.
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.