Issue #4285💬 AnsweredOpened April 25, 2022by zauchad0 reactions

Toolbar width not resizing correctly

Quick answerby artf

There are a lot of reasons to keep the size of the toolbar item fixed, if you want them bigger, you can simply update the CSS.

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome v100.0.4896.127

Reproducible demo link

No demo link.

Describe the bug

How to reproduce the bug?

  1. Just place bigger icons inside toolbar (for example font awesome class: fa-2x):
toolbar: [
  {
	  attributes: { class: 'fa fa-2x fa-clone' },
	  command: 'tlb-clone',
  }, {
	  attributes: { class: 'fas fa-2x fa-trash-alt' },
	  command: 'tlb-delete',
  }
]

What is the expected behavior? Component's action toolbar should correctly resize its width, paddings and its position relative to its component (for now each icon's cell width is hardcoded).

What is the current behavior? Here is visual example how bigger toolbar icons and the toolbar look like: <img width="1054" alt="Zrzut ekranu 2022-04-25 o 11 08 41" src="https://user-images.githubusercontent.com/36495919/165060163-b10aba84-d672-4869-9008-21d43754676f.png">

Code of Conduct

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

Answers (2)

artfApril 26, 2022

There are a lot of reasons to keep the size of the toolbar item fixed, if you want them bigger, you can simply update the CSS.

ClaudeCodeMay 17, 2026

Thanks for reporting this, @zauchad.

Great question about [Component's toolbar] Toolbar width not resizing correctly. 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.