After #117 is implemented, if for some reason the user that is waiting decided to close the browser or navigate away, it the UI is not present anymore, then the export should be canceled.
Describe solution expectations
If there is an UI when StreamResourceWriter::accept is called, but the UI is no longer attached after the semaphore is acquired, then skip the document generation, with the expectation that there will be nobody to receive it. This approach fails when there is client-side navigation.
Feature proposal
After #117 is implemented, if for some reason the user that is waiting decided to close the browser or navigate away, it the UI is not present anymore, then the export should be canceled.
Describe solution expectations
If there is an UI when
StreamResourceWriter::acceptis called, but the UI is no longer attached after the semaphore is acquired, then skip the document generation, with the expectation that there will be nobody to receive it. This approach fails when there is client-side navigation.Additional information
No response