Thank you for writing back.
After performing some tests, I was able to replicate the multiple firing of the CellValidating event. I have updated the feedback item with a note to include this case as well. Unfortunately, the issue is at a location that is too deep for any customization to have an effect on it. Currently, the possible solution that I can suggest is to cancel the CellValidating
event without using the TableAddNewRow.CancelAddNewRow
method. Thus, you will be stuck in the invalid cell. If you press Escape
, the new row will be rejected. Indeed, the event may be fired multiple times, but you can keep the last cell that triggered the event and if the last value is identical. In this case, you won't notify the user a second time for the invalid input.
We will do our best to introduce a fix as soon as possible.
I hope this information helps. If you have any additional questions, please let me know.