It seems that even when using the KeyMap functionality, certain areas of the window to not listen to the KeyMap, such as when you click in the "<Buttons>" area of the following window:

<ext:Window ID="Window1" runat="server" Collapsible="false" Title="Select File(s)" Modal="true" Show&#111;nload="false">
    <Body>
    </Body>
    <Buttons>
        <ext:Button ID="btnOk" runat="server" Text="OK">
        </ext:Button>
        <ext:Button ID="btnCancel" runat="server" Text="Cancel">
            <Listeners>
                <Click Handler="#{Window1}.hide();" />
            </Listeners>
        </ext:Button>
    </Buttons>
    <KeyMap>
        <ext:KeyBinding>
            <Keys>
                <ext:Key Code="ESC" />
            </Keys>
            <Listeners>
                <Event Handler="#{Window1}.hide();" />
            </Listeners>
        </ext:KeyBinding>
    </KeyMap>
</ext:Window>
I thought the KeyMap would mask the issue that hitting the Escape key when certain areas of the window have focus does not have any affect and doesn't close the window. This doesn't seem to work either.

For the current release, is there any code I can add to ensure that no matter where the user last clicked in the window (child controls, caption area, buttons area, etc) a KeyMap on the window can still respond? And, any chance of this being fixed in a future release? This would be more consistent then what is standard functionality (and what users expect) in a desktop app.

Thanks.