Currently we do a lot of work to remember the text selection when there is an error sending an event to the backend. We had to invent a "SerializedRange" object that could be stored in state and rehydrated after a retry/revert. It's a certain amount of complexity, and it's not clear that a user would care, or even notice, about this detail.
Currently we do a lot of work to remember the text selection when there is an error sending an event to the backend. We had to invent a "SerializedRange" object that could be stored in state and rehydrated after a retry/revert. It's a certain amount of complexity, and it's not clear that a user would care, or even notice, about this detail.