Results 1 to 2 of 2

Thread: Ext 4.1: Constructing a KeyNav always results in a deprecation warning in console

    Thank you for reporting this bug. We will make it our priority to review this report.
  1. #1
    Sencha User
    Join Date
    Jul 2010
    Posts
    14
    Vote Rating
    9
      0  

    Default 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."


  2. #2
    Sencha User mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Location
    Gainesville, FL
    Posts
    40,029
    Vote Rating
    1367
      0  

    Default

    Does this happen without the compat layer?
    Mitchell Simoens @LikelyMitch
    Modus Create, Senior Frontend Engineer
    ________________
    Need any sort of Ext JS help? Modus Create is here to help!

    Check out my GitHub:
    https://github.com/mitchellsimoens

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •