Slash commands now block the composer while they execute.

[ara4n]

Steps to reproduce

1. Type a slash command which takes a while - e.g. /invite or /nick
2. Hit enter in the composer
3. Nothing appears to happen.
4. In practice, the command has started to execute in the background, but the composer no longer blanks out until the command has executed.

Outcome

What did you expect?

On hitting enter, the composer should clear and the command should execute in the background.

What happened instead?

On hitting enter, there's no user feedback that the command is being executed at all (even though it is). And you can edit the command in the composer. And run it again. And generally cause chaos.

Operating system

macOS

Application version

today's Nightly

How did you install the app?

No response

Homeserver

matrix.org

Will you send logs?

No

[t3chguy]

On hitting enter, the composer should clear and the command should execute in the background.

I'm not sure I agree, if I get a temporary error I'd want it to be kept there so I can re-execute the command without needing to retype it

there's no user feedback that the command is being executed at all

This is definitely crap though

[MidhunSureshR]

I don't think this is a regression so have removed that label.