Comment 222 for bug 263435

Well the question is: Can we really solve this bug without doing a regression in some case. What we could do is:

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.

Apply keyboard shortcuts for both Flash Content and GUI:
This could have serious side effects in case that flash content does indeed use keyboard strokes. The user would wonder why there are two effects on keystroke.

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.

Any more ideas? 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?' :)