Changes between Initial Version and Version 1 of Ticket #8985, comment 3


Ignore:
Timestamp:
May 22, 2012, 2:39:04 PM (12 years ago)
Author:
Lynne Kues
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #8985, comment 3

    initial v1  
    1 I can only reproduce this inside our application and I do think it is related to running CKE inside dojo and/or our framework.  If the CKE dialog has focus, why is the Enter key event being propagated, which it is and which is then being picked up by our application.  As I indicated, if I change focusKeyDownHandler to consume the event (i.e., evt.stop(); evt.data.preventDefault();), our application doesn't process it, but that's a fix and it's unclear as to why the event doesn't trigger OK like it does in FF.  Any suggestions on how to further debug this?  I am at a bit of a loss and unclear as to why our application would effect this dialog.  We are not extending the table dialog.
     1I can only reproduce this inside our application and I do think it is related to running CKE inside dojo and/or our framework.  If the CKE dialog has focus, why is the Enter key event being propagated, which it is and which is then being picked up by our application.  As I indicated, if I change focusKeyDownHandler to consume the event (i.e., evt.stop(); evt.data.preventDefault();), our application doesn't process it, but that's not a fix and it's unclear as to why the event doesn't trigger OK like it does in FF.  Any suggestions on how to further debug this?  I am at a bit of a loss and unclear as to why our application would effect this dialog.  We are not extending the table dialog.
    22 
© 2003 – 2022, CKSource sp. z o.o. sp.k. All rights reserved. | Terms of use | Privacy policy