Issue #3857πŸ’¬ AnsweredOpened October 8, 2021by flowize-project1 reactions

Firefox issue when the user clicks on different component very fast

Quick answerby arthuralmeidap❀ 1

hello @flowize-project ! hope you are good! In your issue you have posted GrapesJS demo link as reproducible link but the video was recorded with a custom grapesjs installation. Could you try to record a video and reproduce the issue with the GrapesJS demo link??

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Firefox

Reproducible demo link

https://grapesjs.com/demo.html

Describe the bug

How to reproduce the bug? You need to click very fast from one component to another component on the canvas and you will receive a js error "too much recursion" and the html content is gone.

The error is shown in line 1627 model/component.js with method "ensureinlist". We have several customer reporting this issue.

You can check the issue on this video: https://recordit.co/j9e1S6guW5

Thanks.

Code of Conduct

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

Answers (2)

arthuralmeidapβ€’ February 8, 2022

hello @flowize-project ! hope you are good! In your issue you have posted GrapesJS demo link as reproducible link but the video was recorded with a custom grapesjs installation. Could you try to record a video and reproduce the issue with the GrapesJS demo link??

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @flowize-project.

Great question about Firefox issue when the user clicks on different component very fast. 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.