add note why we had to use our own cordsAtPos implementation

ueberdosis · Mar 7, 2019 · 8ddc0c0 · 8ddc0c0
1 parent f490ca1
commit 8ddc0c0
Showing 1 changed file with 2 additions and 0 deletions.
diff --git a/packages/tiptap/src/Plugins/MenuBubble.js b/packages/tiptap/src/Plugins/MenuBubble.js
@@ -81,6 +81,8 @@ class Menu {
     const { from, to } = state.selection
 
     // These are in screen coordinates
+    // We can't use EditorView.cordsAtPos here because it can't handle linebreaks correctly
+    // See: https://github.com/ProseMirror/prosemirror-view/pull/47
     const start = coordsAtPos(view, from)
     const end = coordsAtPos(view, to, true)