Comment 224 for bug 263435

(In reply to comment #222)
> Don't allow keyboard shortcuts in flash content at all: programmers
> would not want that, would they. Especially flash content is
> becoming more complicated and there are many flash applications and
> others using key strokes.

Especially if the developers care the slightest in making their Flash applets accessible. (You might argue "if you want accessibility, don't use Flash" ... but obviously, my point would apply to content that can't feasibly be presented using more accessible technologies.

> Pass keystrokes that are not used from flash content back to the
> GUI: Maybe the best solution. The only problem might be: If flash
> content indeed uses keystrokes like Ctrl+T or something like that,
> then the flash content will process the keystroke although the user
> maybe doesn't want it to do that. I mean: How can a user who wants
> to open a new tab via Ctrl+T know, that the keystroke is used by a
> flash object etc.

Can we tell, in the general case, whether a plugin uses a particular keystroke? To do so would require that the plugin sends feedback to the browser indicating whether it did anything with the keystroke sent to it. But even assuming that this is part of the plugin API, can we rely on all plugins and all Flash objects to get it right?

> Any more ideas?

Why not forward those keystrokes the browser isn't interested in to the plugin?

> I think, we'll end up with a message box 'Hello, do you want to
> adapt this keystroke to the flash object that has focus or do you
> want it to apply on the firefox GUI?' :)

Every time a key is pressed, when this key is used for the first time in a particular plugin session, or what?