Currently you can gate whilst the spinner is showing.
My guess is that this won't crash CE since it deals with files which don't exist yet, or the request timing might be lucky and be handled after the gate has finished but the client hasn't updated.
However, we should probably stop users gating unless the file being shown is an actual, existing file.
As the timeout is never cancelled and only stops being set when the poll limit has been hit, we end up with a sort of race condition where the client is waiting for two gates to finish. My guess is that the first to arrive will be hidden by the second to arrive, which might ultimately be desirable, but probably not in the way it's happening at the moment.
Currently you can gate whilst the spinner is showing. My guess is that this won't crash CE since it deals with files which don't exist yet, or the request timing might be lucky and be handled after the gate has finished but the client hasn't updated. However, we should probably stop users gating unless the file being shown is an actual, existing file. As the timeout is never cancelled and only stops being set when the poll limit has been hit, we end up with a sort of race condition where the client is waiting for two gates to finish. My guess is that the first to arrive will be hidden by the second to arrive, which might ultimately be desirable, but probably not in the way it's happening at the moment.