This question is locked. New answers and comments are not allowed.
If you bind to a ModalView's close event and call e.preventDefault() within it, the close event still continues. Therefore, it appears that there is no way to short-circuit a close event. This seems like a major oversight.
Here's an example: http://trykendoui.telerik.com/@sweffect/ETif/5
(Note that if you open the console and run it, by the time "debugger;" is hit in onClose(), the ModalView is already closed. That seems like a problem.)
On a related note, if the ModalView really needs more events such as the "deactivate" event on the Kendo UI Window widget which fires after the Window is completely closed. Currently, there is no way to know when the ModalView is completely closed which is another problem. It seems like the current ModalView's "close" event is somewhere between the Kendo UI Window's "close" and "deactivate" events. It doesn't clearly act as either and thus is very limited in what it is useful for.
Here's an example: http://trykendoui.telerik.com/@sweffect/ETif/5
(Note that if you open the console and run it, by the time "debugger;" is hit in onClose(), the ModalView is already closed. That seems like a problem.)
On a related note, if the ModalView really needs more events such as the "deactivate" event on the Kendo UI Window widget which fires after the Window is completely closed. Currently, there is no way to know when the ModalView is completely closed which is another problem. It seems like the current ModalView's "close" event is somewhere between the Kendo UI Window's "close" and "deactivate" events. It doesn't clearly act as either and thus is very limited in what it is useful for.