Editor's selection points to non-existing location when value is changed programmatically (Chrome, Safari)

Do you want to request a feature or report a bug?

Bug.

What’s the current behavior?

https://codesandbox.io/s/slate-reproductions-forked-lzc7g?file=/index.js

1. Focus the last paragraph in the example
2. Click “Reset” button

useSlate().selection points to a non-existing location (location after performing step (1))

Slate: 0.58.4 Browser: Chrome, Safari OS: Windows, Linux, Mac

What’s the expected behavior?

useSlate().selection points to an existing location.

Works fine in Firefox.

[DaniGuardiola]

@e1himself on a second thought, it might not be necessary to distinguish those, but I’m still worried that it’ll be already too late and the editor would’ve crashed by then, since the value would’ve been applied already.

[DaniGuardiola]

@e1himself yep, I think that’s the problem with that fix, I don’t think there a good way to tell which is which.

@kamilmielnik in our case we have quite a few places where we’re accessing the selection, so checking everywhere would be a little messy 😕 thx for sharing though!