fix(slate-dom): propagate suppressThrow to toSlateNode in toSlatePoint (#6072)

* fix(slate-dom): propagate suppressThrow through toSlateNode in toSlatePoint

When toSlatePoint is called with suppressThrow: true, errors thrown by
toSlateNode were not being suppressed — only errors from findPath were
handled. Wrap the toSlateNode call in the same try/catch pattern already
used for findPath.

This is the gap left by PR #6004 which guarded findPath but not the
preceding toSlateNode call.

* chore: add changeset for toSlatePoint suppressThrow fix

* Prettier fix

Author: pangoyal-gong

.changeset/fix-toSlatePoint-suppress-throw.md

@@ -0,0 +1,5 @@
+---
+'slate-dom': patch
+---
+
+Fix `toSlatePoint` not respecting `suppressThrow` when `toSlateNode` throws. Only errors from `findPath` were guarded; errors from the preceding `toSlateNode` propagated unconditionally even with `suppressThrow: true`.

packages/slate-dom/src/plugin/dom-editor.ts

@@ -920,7 +920,15 @@ export const DOMEditor: DOMEditorInterface = {
     // COMPAT: If someone is clicking from one Slate editor into another,
     // the select event fires twice, once for the old editor's `element`
     // first, and then afterwards for the correct `element`. (2017/03/03)
-    const slateNode = DOMEditor.toSlateNode(editor, textNode!)
+    let slateNode
+    try {
+      slateNode = DOMEditor.toSlateNode(editor, textNode!)
+    } catch (e) {
+      if (suppressThrow) {
+        return null as T extends true ? Point | null : Point
+      }
+      throw e
+    }
     let path
     try {
       path = DOMEditor.findPath(editor, slateNode)