Having a strange problem with IgniteUI grid (15.2). I created an editor dialog hooked up to edit row values. This is working great except for one weird keyboard problem.
I've got a handler attached to "iggridupdatingeditroweneded"...this fires correctly when clicking the Done or Cancel buttons in the editor, every time. If, however, after a page refresh, I instead try to use ESC or ENTER instead of clicking the Done or Cancel buttons, the "iggridupdatingeditroweneded" event will not fire. But, as soon as I once use the Done or Cancel buttons in the editor, thereafter, until a page refresh, pressing ESC or ENTER *will* trigger the event, and it works as I expect (that is, pressing ENTER acts as "Done" and pressing ESC acts as "Cancel". It's only until I first click Done or Cancel in the editor that the keyboard doesn't work (for any row).
I'm not sure if I've got something wired up wrong or what, hoping someone can shed some light on what's going on here.
Thank you.
Hello Doug,
Unfortunately, this is a bug and I logged it with #216603 in our internal tracking system. A support case is created on your behalf with number CAS-171245-F8C1M8, so that you can be notified when the bug is fixed.
You can find your active cases under Account - Support Activity in our website. Select your ticket and go to Development Issues tab to view the status of related bugs.
If the issue is critical for your development effort I can suggest the following workaround:
$("#grid").bind("iggridupdatingeditrowstarted", function (evt, ui) { ui.owner._dialogClosingFromUI = true; });
This presumes the dialog will be closed with the dialog's UI and should be safe unless you plan on having it close-able by the use of the public API.
I hope this helps! Please, let me know if you have any other questions or concerns!
Best regards,
Stamen Stoychev
OK, thank you for the update/information and workaround, will give that a go. This isn't a deal-killer, worst-case we can just make sure that folks know they need to click the buttons. I appreciate the help.
The fix for development issue 216603 is available in the latest service release which can be downloaded from the My Keys and Downloads page.