You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Text main branch the drag handler is no longer visible. On stable32 it works as expected. I wonder whether it's related to the Tiptap3 migration.
The component is loaded and onNodChange() is triggered, but the component element (.floating-buttons) always stays hidden. Looking at its ancestors, it doesn't seem to be mounted to the document either.
This recent upstream Github issue might be related (they use the vue3 plugin though): ueberdosis/tiptap#7282
EDIT: appendChild() works as expected, but when it happens, the editor element itself is a child of a "lonely" div element that is not attached to the HTML document (yet).
Indeed seems to be a kind of race condition. The following patch fixes the problem by waiting for the editor component to be visible before mounting the floating button component:
Activity
mejo- commentedon Dec 16, 2025
I further debugged this a bit and apparently
showHandle()andhideHandle()from https://github.com/ueberdosis/tiptap/blob/9d7ea8d2f9099f4d3ffe5e093beeee72e7c8722e/packages/extension-drag-handle/src/drag-handle-plugin.ts#L90-L111 are called as expected. Thevisibilitystyle property is also updated correctly. The problem rather seems to be that the whole<div>element containing the drag handle is not attached to the HTMLdocument.mejo- commentedon Dec 16, 2025
https://github.com/ueberdosis/tiptap/blob/9d7ea8d2f9099f4d3ffe5e093beeee72e7c8722e/packages/extension-drag-handle/src/drag-handle-plugin.ts#L238 is the place where the wrapper element should get appended to the editor element parent. But for some reason, even though
appendChild()is called according to the debugger, afterwardswrapper.parentElementis still a lonelydivelement that has no further parents.EDIT:
appendChild()works as expected, but when it happens, the editor element itself is a child of a "lonely"divelement that is not attached to the HTMLdocument(yet).mejo- commentedon Dec 16, 2025
Indeed seems to be a kind of race condition. The following patch fixes the problem by waiting for the editor component to be visible before mounting the floating button component:
mejo- commentedon Dec 18, 2025
I opened ueberdosis/tiptap#7350 to fix the issue upstream.
mejo- commentedon Dec 22, 2025
Yay, fixed by #8093.