Issue #3873πŸ’¬ AnsweredOpened October 19, 2021by JGiard0 reactions

Duplicated video block when re-attaching GrapesJs editor to document

Quick answerby JGiard

I've created a pull-request with what I would expect a fix to look like, given my understanding of the issue.

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome v94

Reproducible demo link

https://jsfiddle.net/3mrzaqtx/

Describe the bug

How to reproduce the bug?

  1. Add a video block to the canvas
  2. Remove the GrapesJs editor element from the document (Optional)
  3. Re-attach the GrapesJs editor element to the document

What is the expected behavior? GrapesJs canvas should be the same before and after the operation

What is the current behavior? The video is displayed multiple times

My investigation According to the ComponentVideoView, this is caused by the render() function. Unlike the updateProvider() function, render doesn't take care of clearing the container before appending the new iframe/video tag in the block.

We are integrating GrapesJs into another application, and we don't create a new GrapesJs editor when switching back and forth between views, thus the detach/attach behavior. I also don't know what events GrapesJs listens to trigger a re-render on attach.

Code of Conduct

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

Answers (3)

JGiardβ€’ October 19, 2021

I've created a pull-request with what I would expect a fix to look like, given my understanding of the issue.

artfβ€’ October 20, 2021

No, you should never rely on something like this, or you destroy and reinit, or you simply hide and show the editor.

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @JGiard.

Great question about Duplicated video block when re-attaching GrapesJs editor to document. 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.