Issue #3243💬 AnsweredOpened January 20, 2021by hanna4040 reactions

Textable attribute not working and causing exceptions

快速解答by artf

Duplicate of #2771

Read full answer below ↓

Question

Version: 0.16.27 to latest

Are you able to reproduce the bug from the demo? Yes [ X] Yes [ ] No

What is the expected behavior? insert text block inside another text block Describe the bug detailed

when adding new block, or even when creating a new custom type, the "textable attribute is not working as expected and as described. Nothing similar was reported before, image

image

What is the current behavior? i am getting an error when dragging and dropping the element (as you can see the images attached, I am trying on the demo locally , the added element is : ` editor.BlockManager.add('my-text-test', { label: 'Simple map block', content: { type: 'text', removable: true, content:'test',
droppable: true, highlightable:1, copyable:true, draggable: 1, editable:1, textable: 1

} })`

let me know if further details are required i will be happy to share them, thank you Descripe the bug detailed

Are you able to attach screenshots, screencasts or a live demo?

[ X] Yes (attach) [ ] No

Answers (2)

artfJanuary 27, 2021

Duplicate of #2771

ClaudeCodeMay 17, 2026

Thanks for reporting this, @hanna404.

The issue with Textable attribute not working and causing exceptions appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifications overlap, creating an inconsistent state.

What to try:

  1. Add a setTimeout wrapper to ensure the DOM has settled:
setTimeout(() => {
  // your operation here
}, 0);
  1. Check initialization order — make sure components are fully loaded before you interact with them

  2. Use the editor's event system — listen to completion events:

editor.on('component:mount', (component) => {
  // safe to interact with component here
});

Recommended next steps:

  • Test with the latest GrapesJS version if you haven't
  • Provide a minimal reproducible example (CodeSandbox) — this helps the team identify the root cause faster
  • Include GrapesJS version, browser, and console errors in your report

Related Questions and Answers

Continue research with similar issue discussions.

Paid Plugins That Match This Issue

Curated by issue keywords and label relevance to help you ship faster.

View all plugins

Loading paid plugin recommendations...

Free option

Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.

Browse free plugins →
Premium option

Premium plugins ship with support, regular updates, and production-ready features — save days of integration work.

Browse premium plugins →

Related tutorials

In-depth guides on the same topic.

All tutorials →

Browse Plugin Categories

Jump directly to plugin category pages on the marketplace.