Page 2 of 2 FirstFirst 12
Results 11 to 14 of 14

Thread: Error raised when fireing an event on already destroyed component

    Success! Looks like we've fixed this one. According to our records the fix was applied for EXTJS-22909 in 6.5.2.
  1. #11
    Sencha User
    Join Date
    Feb 2013
    Location
    California
    Posts
    11,985

    Default

    No, apologies for not being more clear. 6.5.2 and 6.2.2 are still a nightly releases, which generally are not recommended for production.

  2. #12
    Sencha User
    Join Date
    Jul 2017
    Posts
    64

    Default

    After having upgraded ExtJS to 6.5.2.463, I still seem to be experiencing this bug. I am destroying an Ext.dd.DD object before its onMouseUp event is fired.
    asdf.png

  3. #13
    Sencha Premium Member
    Join Date
    Nov 2013
    Posts
    160

    Default

    Just upgraded to version 6.5.3.57 and this bug is STILL NOT FIXED.

    [W] Attempting to fire "keydown" event on destroyed ParClient.view.virtuallocation.VirtualDisplayLocationEditWindow instance with id: ext-comp-1105
    ext-all-debug.js:10025:21
    [W] Attempting to fire "keydown" event on destroyed Ext.util.KeyMap instance with id: unknown
    ext-all-debug.js:10025:21
    When will this actually be fixed?

  4. #14
    Sencha Premium User
    Join Date
    Feb 2017
    Posts
    43

    Default

    I am still seeing this on 6.5.3 as well.

Page 2 of 2 FirstFirst 12

Similar Threads

  1. Problem with event fireing
    By noway in forum Ext 5: Q&A
    Replies: 3
    Last Post: 5 May 2014, 10:13 AM
  2. Replies: 0
    Last Post: 4 Nov 2009, 4:15 PM
  3. Replies: 8
    Last Post: 8 Jul 2008, 12:51 AM
  4. Event Raised For Connection Timeout
    By herrjj in forum Ext 2.x: Help & Discussion
    Replies: 3
    Last Post: 2 Jul 2008, 8:58 AM

Posting Permissions

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