It seems (OP correct me if I'm wrong) that it uses actual browser events, which are asynchronous (where normally Redux messages are sent and reacted-to synchron

It seems (OP correct me if I'm wrong) that it uses actual browser events, which are asynchronous (where normally Redux messages are sent and reacted-to synchronously). This probably simplifies things when you do want asynchronous chains of events, but complicates things when it comes to UI consistency and race conditions.