The following code-library provides extensive information on the "blocking the browser execution thread" issue:
You will notice that contrary to all the details provided, every once in a while there is a comment from someone claiming that this functionality is implemented in a difficult manner and can be made easier to use, as well as claims suggesting that in fact, it would be somehow possible to block the browser execution thread... if only Telerik wanted to try. Unfortunately, neither of this is true. Despite our best efforts.
In addition, there is no universal solution that can cover all scenarios in the same manner. So, technically speaking, "I
am still expecting Telerik to provide us with a radConfirm blocking
solution working with every rad control subject to send callback." is not
likely to happen any time soon.
To keep a long story short (you can read the longer version in the provided thread):
cannot block the browser execution thread like buil-in browser confirm
2) In some scenarios, however, it is possible to simulate as if this happens.
3) However, in many more scenarios this is not possible - then, in case you wish to use radconfirm
instead of confirm
, you will need to provide a callback function to be called after the uses closes the popup.
The Dock scenario is just one such case (#3)
the Telerik team
, the state of the art learning tool for Telerik products.