Thank you for reporting this bug. We will make it our priority to review this report.
Ext 4.1: Constructing a KeyNav always results in a deprecation warning in console
I'm seeing this in 4.1.0. Apparently, there is no way to construct a KeyNav without generating a compatibility layer error. The logic in the compatibility layer that determines if an error should be logged is, well, bizarre to say the least. It's causing the following message to appear over and over again in my js console: "[DEPRECATED][4.0][KeyMap]: Ext.KeyMap has been deprecated, use Ext.util.KeyMap."
Does this happen without the compat layer?