Comment 245 for bug 263435

Mixing Comment 233 and Comment 236:

0.Spec new plugins to bubble up non-used keystrokes
1.Before a plugin is accessed, all strokes are sent to the browser attention
2.When a plugin is clicked or accessed somehow, it gets focus (the GUI could make it obvious by graying the tab or something)
3.Keystrokes are, from then on, all sent to the plugin (except F6)
4.Display some advice for the user saying special content is activated and to click somewhere or press F6 to exit (maybe different advices for spec'd and old plugins)*
5.F6 alternates focus between browser (meaning all menus, tab control, address bar, buttons, etc.) and contents (plugin)
6.When focus is changed to the browser or the user swithches tab (in response to Comment #194), behaviour is back to 1.

This way: the browser will work as expected; the plugin, when activated, also will; the user has a better feel on what to expect (browser-like or plugin-like behaviour); and user can control it better.

As correctly pointed out by some, users have no idea of what a plugin is. But this approach will at least make them know they're inside a pdf or a flash or whatever and letting an easy and visible wat "to get back to Firefox".

At least, this would be the optimal behaviour for me, as an user standpoint.

*Very long suggestion: "Special contents activated. Click in a tab, menu or the address bar or press F6 to exit and reactivate Firefox shortcuts." shown in the status bar.

Many thanks