Comment 3 for bug 263435

Okay, looked closer at this. There are two bugs here. First, "lost focus" wasn't
working. Typo, should be using NS_CONTENT_BLUR instead of NS_LOSTFOCUS. Need
to double check that it won't cause regressions on other platforms, but once
that was fixed, one can click outside the plugin content area and then command
keys work as expected. In fact, you could scroll the page with the keyboard and
other key events seem to work.

The other problem is that the plugin was consuming all key events. Perhaps Peter
G. from Macromedia knows if Shockwave returns consume status on keys like this
or if Nav was responsible for filtering them out.

Even after returning nsEventStatus_eIgnore from the DOM key event in
nsObjectFrame.cpp if a "meta" key was down, it still looked like my event was
consumed. Probably need to set some breakpoints in the EventStateManager.
Pinkerton or Saari, do you have any tips on debugging this on the Mac? I wonder
if there is a way to process shortcut keys before sending the event to the DOM.