ueberdosis/tiptap · error
FloatingMenu component is not rendered inside of an editor c
Error message
FloatingMenu component is not rendered inside of an editor component or does not have editor prop.
What it means
Error "FloatingMenu component is not rendered inside of an editor component or does not have editor prop." thrown in ueberdosis/tiptap.
Source
Thrown at packages/react/src/menus/FloatingMenu.tsx:93
/**
* Track whether the plugin has been initialized, so we only send updates
* after the initial registration.
*/
const [pluginInitialized, setPluginInitialized] = useState(false)
/**
* Track whether we need to skip the first options update dispatch.
* This prevents unnecessary updates right after plugin initialization.
*/
const skipFirstUpdateRef = useRef(true)
useEffect(() => {
if (pluginEditor?.isDestroyed) {
return
}
if (!pluginEditor) {
console.warn(
'FloatingMenu component is not rendered inside of an editor component or does not have editor prop.',
)
return
}
const floatingMenuElement = menuEl.current
floatingMenuElement.style.visibility = 'hidden'
floatingMenuElement.style.position = 'absolute'
const plugin = FloatingMenuPlugin({
...floatingMenuPluginPropsRef.current,
editor: pluginEditor,
element: floatingMenuElement,
})
pluginEditor.registerPlugin(plugin)
const createdPluginKey = floatingMenuPluginPropsRef.current.pluginKeyView on GitHub (pinned to 496d53afd7)
When it happens
Trigger: Thrown at packages/react/src/menus/FloatingMenu.tsx:93 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of ueberdosis/tiptap@496d53afd7 (2026-08-26).
Data as JSON: /api/errors/a97c5ff5675027c4.
Report an issue: GitHub.