ianhitchman/tiptap
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

add note why we had to use our own cordsAtPos implementation

Browse Source
This commit is contained in:
Chrissi2812
2019-03-07 18:15:45 +01:00
parent f490ca1469
commit 8ddc0c016a
1 changed files with 2 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
packages/tiptap/src/Plugins/MenuBubble.js
View File

@@ -81,6 +81,8 @@ class Menu {
const { from, to } = state.selection const { from, to } = state.selection
// These are in screen coordinates // 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 start = coordsAtPos(view, from)
const end = coordsAtPos(view, to, true) const end = coordsAtPos(view, to, true)