Wijmo Grid quick edit, event cellEditEnded not triggered

Wijmo Grid quick edit, event cellEditEnded not triggered

Posted by: bozjator on 13 November 2019, 10:51 pm EST

• 

  bozjator

  • Post Options:
  • Link
    Copy

  Posted 13 November 2019, 10:51 pm EST

  Hello

  I noticed that event cellEditEnded is not triggered if user, after editing a cell, is using arrow keys left / right or clicking on the same row. (so if he stays on the same row event cellEditEnded is not triggered)

  But if user press enter, on use arrow keys up / down, or clicks outside of the row in which cell was edited, then event cellEditEnded is triggered.

  Is this a bug in wijmo grid or is there any other ways to also detect that edit ended if user stays in the same row after editing a cell?

  Regards

• 

  ashwin.saxena

  

  • Post Options:
  • Link
    Copy

  Posted 14 November 2019, 5:08 pm EST

  Hi Blaž,

  We are sorry but we were not able to replicate the issue at our end. Please refer to the sample below that we used to replicate the issue:

  https://stackblitz.com/edit/js-ukno4u

  Could you please tell us whether we are missing something or you may modify the sample so that it replicates the issue. Could you also let us know which version you are currently using?

  Regards,
  
  Ashwin

• 

  bozjator

  • Post Options:
  • Link
    Copy

  Posted 26 November 2019, 2:08 am EST

  Sorry, my mistake.
  
  cellEditEnded was called also when navigating by arrows in the same row.
  
  By changing one cell value, i was changing some other cells too, but for some reason the new values were not shown when navigating by arrows in the same row.
  
  Now i call refresh on the grid, after cell is edited and new values are then shown.

  Regards

• 

  ashwin.saxena

  

  • Post Options:
  • Link
    Copy

  Posted 26 November 2019, 3:22 pm EST

  Hi Blaž,

  Please refer to the sample below:

  https://stackblitz.com/edit/js-lmgwgg

  In this sample, if you will edit the Downloads column, the data in the Expenses column will be updated.

  Could you please confirm whether this is the behavior you were expecting?

  ~regards