Easy repro crash when triple clicking

[scottlu]

Description

Very easy to reproduce crash. Simply triple click in an area of Editable not occupied by a child element. See Context below for the lines of code that are causing it.

The bug was introduced very recently, 4/4/22, PR #4914, meant to fix issue #3871

Recording

simplescreenrecorder-2022-04-07_20.35.13.mp4

Sandbox

https://codesandbox.io/s/slate-reproductions-forked-j0e6qq

Steps
To reproduce the behavior:

1. Open the sandbox
2. Ensure the sandbox is using slate 0.76.1, slate-react 0.76.1, and slate-history 0.66.0
3. Triple click in the Editable's padding area, not on the child element
4. Crash

Expectation

Not to crash.

Environment

• Slate Version: slate 0.76.1, slate-react 0.76.1, slate-history 0.66.0
• Operating System: [Debian Bullseye]
• Browser: [Chrome]

Context

The problem is the TRIPLE_CLICK code merged on 4/4/22, PR #4914, in slate-react/src/components/editable.tsx, line ~1503. In the case of triple clicking on the Editable component itself, the node returned from toSlateNode is the editor node, and the path returned from findPath is of zero length. The code inside the TRIPLE_CLICK conditional appears to not take into account the the node is the editor, or that the path length may be zero.

[benbrandt]

Also seeing this behavior

[zijizhu]

Yeah I can also reproduce this. Any potential fix?

[JosNun]

Is this fixed by #4944?

[BitPhinix]

Yes, this can be closed