Issue #3266💬 AnsweredOpened February 9, 2021by amliu0 reactions

How to know from which block is the selected component generated ?

快速解答by artf

You should think more about components than blocks, indeed the right Block should look more like that. But in case you need it, you can always attach custom properties to your content block (which then will be appended to the component) Once that block is dropped you will always be able to get that property component....

Read full answer below ↓

Question

Wondering how to do a reverse lookup, from component back to block.

I use Block Manager add() to add a block like below after initialization.

editor.BlockManager.add(
  'my-module-id', 
  {
    label: ...
    content: editor.getSelected().toHTML(),
   category: ...
  }
}

How do I if the selected component is generated by this custom block ?

Answers (2)

artfFebruary 19, 2021

You should think more about components than blocks, indeed the right Block should look more like that.

editor.BlockManager.add('block-id',  {
    label: ...
    content: { type: 'component-id' },
})

But in case you need it, you can always attach custom properties to your content block (which then will be appended to the component)

editor.BlockManager.add('block-id',  {
    label: ...
    content: { type: 'component-id', fromBlock: 'block-id'  },
})

Once that block is dropped you will always be able to get that property component.get('fromBlock')

ClaudeCodeMay 17, 2026

Thanks for reporting this, @amliu.

Great question about [Question] How to know from which block is the selected component generated ?. The recommended approach with Components is to use the event-driven API.

Start here:

  1. Check the GrapesJS documentation for your specific module
  2. Look for the on() event listener method
  3. Most operations can be achieved by listening to editor and component events

Common patterns:

// Listen for changes
editor.on('change', () => console.log('something changed'));

// Component lifecycle
editor.on('component:mount', (c) => console.log('component ready', c));
editor.on('component:update', (c) => console.log('component updated', c));

If you're still stuck:

  • Share a minimal CodeSandbox reproduction
  • Include what you've already tried
  • Mention your GrapesJS version
  • The community is here to help!

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.