[cvvParticipant]

Hello Christopher!
Thank you for your reply.

Personally (as well as our QA team) I don’t think that such behaviour is normal: a floating popup which behaves like it’s part of the window (and any user thinks so) and later it turns out to be a separate window (without header or whatever).
It’s not what a user expect to see.

Your workaround to destroy the window is not what I could use, for I need to open and close the window arbitrarily, and if I just destroy it – it messes up the DOM structure.

Is there any better solution?

[cvvParticipant]

Hello Hristo!
Thank you for your answer.
But in fact, unfortunately, it doesn’t solve my problem.

Answering your question: There are no any errors in the console, everything is fine.

Once again:
I’m performing a server-side validation of the data (in addition to client-side).
For example, I want to have only unique values for some columns or any other business logic.
Once the validation fails I send HTTP 500 response with the error message to the client.

My “error:” function gets called, I display the message to the user and perform “commit(false)”
I would expect the data in the grid to keep its original (first loaded) state, but it doesn’t:

1) Right after the action the grid shows the original (unmodified) data, but once I refresh the view (for example, change any column width) it displays the modified (rejected) data.
2) If I execute jqxGrid(‘getrowdata’) on the same row for the second time (after commit(false)) it returns modified (rejected) data.

I’ve been able to fix that if I perform grid reload .jqxGrid(‘updatebounddata’) right after commit(false), but it’s not a desirable fix because of paging functionality which gets broken this way.

Thanks!

[Author]

Posts