Rather than generating many individual keypress-like events, the standard trace just makes one textInput event that has all the data we want to add, speeding the process.  Note that this could make things like the Southwest example --- with custom handlers attached to arbitrary events --- fail.
Preventing replayer from using compensation functionality to overwrite the changes made with textInput to the change made by the original textInput event from which it's cloned.