I was experimenting promises and as I understand, as pointed out in issue #23, an async process running for the same user is supposed to block execution of all other intra-session activities. However this doesn't seem to be a universal principle.
In the example app below, I have an artificially drawn out plotting operation and some other elements to see how they interact. One of these elements is a downloadButton/downloadHandler pair. While the async operation is running, it is still possible to press the downloadButton and get an input, which was unexpected for me. In fact before the first 10 seconds, the downloadButton still works but pretends downloadHandler isn't there and downloads the whole page. After the first 10 seconds, downloadButton will download the intended file immediately even if an async process is running. My questions are:
I was experimenting promises and as I understand, as pointed out in issue #23, an async process running for the same user is supposed to block execution of all other intra-session activities. However this doesn't seem to be a universal principle.
In the example app below, I have an artificially drawn out plotting operation and some other elements to see how they interact. One of these elements is a
downloadButton
/downloadHandler
pair. While the async operation is running, it is still possible to press thedownloadButton
and get an input, which was unexpected for me. In fact before the first 10 seconds, thedownloadButton
still works but pretendsdownloadHandler
isn't there and downloads the whole page. After the first 10 seconds,downloadButton
will download the intended file immediately even if an async process is running. My questions are:downloadHandler
special?