how can an application (flash or javascript) know what keystroke combinations are going to be grabbed by the browser?
I run in to this situation with a javascript app (shell in a box, running command line tools on a remote machine), on firefox the <cntl> T goes to the app, on chrome it goes to the browser.
which is better? having some portions of the app unavailable? or having some portions of the browser unavailable?
in my case it's more annoying to have the portions of the app unavailable, but I can understand how other people would want it the other way.
the particular command-line app that I run into trouble with most frequently pre-dates the start of firefox, let alone chrome, so you can't blame the app for using a 'reserved' key combination.
think about this a bit more, how can a browser know what key combinations are reserved by the Desktop Environment? what should happen if you have a conflict there?