Issue #3475πŸ’¬ AnsweredOpened May 24, 2021by ThetripGr0 reactions

Toolbar/actionbar buttons do not work when there are multiple instances present (Even in your demo)

Quick answerby artf

Thanks for the report @DodoTrip The fix is ready for the next release.

Read full answer below ↓

Question

Version: 0.16.44

You can get the version by typing grapesjs.version into the console

Are you able to reproduce the bug from the demo?

  • Yes
  • No

What is the expected behavior? Every instance has their own toolbar working properly

Describe the bug detailed So previously i made another issue relating to instances #3354 , in this issue i conclude that it was my fault handling the instances improperly . Here i even stumble upon the bug even in the demo page https://grapesjs.com/docs/getting-started.html#theming. You can see that in every single instance no toolbar works, none of the options provided ( bold,strikethrough, link etc ), except the very last initiated instance. This also is what happening on my case ( toolbar only works on the last initiated instance ).

Are you able to attach screenshots, screencasts or a live demo? You can test this on the getting started demo page https://grapesjs.com/docs/getting-started.html#theming

  • Yes (attach)
  • No

Answers (2)

artfβ€’ June 13, 2021

Thanks for the report @DodoTrip The fix is ready for the next release.

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @ThetripGr.

The issue with Toolbar/actionbar buttons do not work when there are multiple instances present (Even in your demo) 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.