I think there is an issue with 1.4.31 – where modal forms ( displayed with .ShowDialog() ) are not blocking code execution as expected – IF you are not using webSockets. I updated to the new release today (1.4.31) and started seeing this issue because my dev machine is Windows 7 and my IIS Express cannot support websockets.
I deployed the project to my server – which supports web sockets – and the problem went away. As a test – I disabled web sockets in my json.default file – then re-deployed to the website and the problem was there.
As a test – I downgraded to 1.4.25 – and this behavior went away even when websockets are not enabled. So I think it is a regression that may have surfaced somewhere between 1.4.25 and 1.4.31.
Attached is a small sample that will illustrate the problem if you have websockets turned off and use 1.4.31. I can live with 1.4.25 for a little while – but please advise.
Thanks very much,
Matthew
Hi Matthew,
thanks ! This non-websocket scenario seems to have “slipped” through our testings.
We are constantly improving that so we will make sure to cover it better for the next releases.
We have replaced 1.4.31 with 1.4.32 now that fixes the problem with modal dialogs being non blocking when not using web sockets.
The new build has just been uploaded.
Best regards
Frank
Thanks very much! That was truly quick. We confirm 1.4.32 fixes this issue on our side.
Please login first to submit.
