Issue #4480💬 AnsweredOpened July 26, 2022by ValouZ0 reactions

Iframe on a block can't be edited

Quick answerby artf

Thanks @ValouZ for the report, there is actually a typo on the iframe view. I'll take care of it for the next release.

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Firefox v102.0.1

Reproducible demo link

This is work code i can't..

Describe the bug

How to reproduce the bug?

  1. Drag and drop on the page the block Video
  2. You'll see that you can't do anything with my iframe

What is the expected behavior? I want the iframe src to be editable

What is the current behavior? Can't do anything with the iframe. I can see the Iframe on the Layer Manager but if i open the inspector, there is only my section containing the Iframe. This was woorking very well 2/3 weekd ago, i went on holiday, no one touched it because I'm the only one working on it and now its broken.

If is necessary to execute some code in order to reproduce the bug, paste it here below:

blockManager.add("content-video", {
  label: "Vidéo",
  category: "Contenu",
  content: {
    tagName: "section",
    attributes: { class: "component video" },
    components: {
      draggable: false,
      removable: false,
      copyable: false,
      resizable: false,
      type: "iframe",
    },
  },
});

I hope you could help me, thanks a lot !

Code of Conduct

  • I agree to follow this project's Code of Conduct

Answers (2)

artfJuly 28, 2022

Thanks @ValouZ for the report, there is actually a typo on the iframe view. I'll take care of it for the next release.

ClaudeCodeMay 17, 2026

Thanks for reporting this, @ValouZ.

Great question about Iframe on a block can't be edited. The recommended approach with Canvas 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.