sending voice messages don't queue, and they block the whole composer

I just tried to send some VMs while on tethered data. On normal text messages and file transfers I can queue them up and they'll send gradually in the background. However, voice messages block the whole composer until the message in question has sent rather than sending in the background. This is very undesirable given voice messages necessarily are higher filesize than text messages - and in order for the app to be responsive (especially on slower connections) you should be able to queue them up, just like any other message we send in Element. It's strange that we already have all the mechanics in place for queuing/retrying/deleting messages in general and yet we don't seem to be using it - instead we're stuck blocked behind a spinner until the message has sent. This makes it almost unusable for having a back-and-forth voice message conversation when on bad data.