flex - wasd - keyboard events javascript

Capturing Cmd-C(or Ctrl-C) keyboard event from modular Flex application in browser or AIR (4)

It seems that it is impossible to capture the keyboard event normally used for copy when running a Flex application in the browser or as an AIR app, presumably because the browser or OS is intercepting it first.

Is there a way to tell the browser or OS to let the event through?

For example, on an AdvancedDataGrid I have set the keyUp event to handleCaseListKeyUp(event), which calls the following function:

        private function handleCaseListKeyUp(event:KeyboardEvent):void
            var char:String = String.fromCharCode(event.charCode).toUpperCase();

            if (event.ctrlKey && char == "C")

            if (!event.ctrlKey && char == "C")

            // Didn't match event to capture, just drop out.
            trace("charCode: " + event.charCode);
            trace("char: " + char);
            trace("keyCode: " + event.keyCode);
            trace("ctrlKey: " + event.ctrlKey);
            trace("altKey: " + event.altKey);
            trace("shiftKey: " + event.shiftKey);

When run, I can never get the release of the "C" key while also pressing the command key (which shows up as KeyboardEvent.ctrlKey). I get the following trace results:

charCode: 0
keyCode: 17
ctrlKey: false
altKey: false
shiftKey: false

As you can see, the only event I can capture is the release of the command key, the release of the "C" key while holding the command key isn't even sent.

Has anyone successfully implemented standard copy and paste keyboard handling?

Am I destined to just use the "C" key on it's own (as shown in the code example) or make a copy button available?

Or do I need to create the listener manually at a higher level and pass the event down into my modular application's guts?

Another incredibly annoying thing that I just realized is that ctrl-c can't be captured by event.ctrlKey && event.keyCode = Keyboard.C (or ...event.charCode == 67), instead you have to test for charCode or keyCode being 3. It kind of makes sense for charCode since ctrl-c is 3 in the ASCII table, but it doesn't make sense for keyCode, which is supposed to represent the key on the keyboard, not the typed character. The same goes for all other key combos (because every ctrl combo has an ASCII equivalent).

Edit Found a bug in the Flex bug system about this: https://bugs.adobe.com/jira/browse/FP-375

I did a test where I listened for key up events on the stage and noticed that (on my Mac) I could capture control-c, control-v, etc. just fine, but anything involving command (the  key) wasn't captured until I released the command key, and then ctrlKey was false (even though the docs says that ctrlKey should be true for the command key on the Mac), and the charCode was 0. Pretty useless, in short.

Flex AIR using Command and Ctrl keyboard events

In this basic AIR example I caught both CMD and CTRL keys:

<?xml version="1.0" encoding="utf-8"?>
<mx:WindowedApplication xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute">
        trace('CharCode: ' + event.charCode + ' Cmd: ' + event.commandKey + ' Ctrl: ' + event.ctrlKey + ' KeyCode: ' + event.keyCode);
    <mx:TextArea />

I know I had really a lot problem with keyboard events in Flex and either AIR apps because of focus. In the example above you will only see proper results if you click into the Textarea. Maybe this is how it should work by default but I still find keyboard event handling pain in Flex.