Mozilla took different approach to Chrome - Chrome decided to take back keyboard, FF doesn't want to harm Flash plug-ins that might be using it. That is also why Roth's patch was rejected.
When Flash adopts the NPAPI proposal and makes necessary changes, so will Mozilla. No sooner will this be fixed than that, because otherwise it's hard to test.
I recommend closing this / marking as "won't fix" with appropriate comment "waiting for Adobe".
If someone has information why the approach "not to take back keyboard unless Flash allows us to" was chosen, please share. I'd say it's wrong approach, but my perspective is personal, and perhaps there are facts speaking in favour for plug-ins.
PS. A bit of irony: under the window I'm writing this in, there's "Status: NEW". :-)
Mozilla took different approach to Chrome - Chrome decided to take back keyboard, FF doesn't want to harm Flash plug-ins that might be using it. That is also why Roth's patch was rejected.
When Flash adopts the NPAPI proposal and makes necessary changes, so will Mozilla. No sooner will this be fixed than that, because otherwise it's hard to test.
I recommend closing this / marking as "won't fix" with appropriate comment "waiting for Adobe".
If someone has information why the approach "not to take back keyboard unless Flash allows us to" was chosen, please share. I'd say it's wrong approach, but my perspective is personal, and perhaps there are facts speaking in favour for plug-ins.
PS. A bit of irony: under the window I'm writing this in, there's "Status: NEW". :-)