Issue #4138💬 AnsweredOpened February 12, 2022by yadavAtIrisdame0 reactions

Unexpected behavior in style manager

快速解答by artf

Thanks for the report @yadavAtIrisdame but I'm not able to reproduce it from your demo or the official one. Can you describe the exact steps?

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Version 1.35.101 Chromium: 98.0.4758.87 (Official Build) (64-bit)

padding

Reproducible demo link

https://codesandbox.io/s/strange-sun-qgdcq?file=/index.js

Describe the bug

How to reproduce the bug?

  1. drop the component in canvas
  2. select the component and apply some margin and padding

What is the expected behavior? ...should apply margin and padding when we give some margin and padding.

What is the current behaviour? Sometimes it is working and sometimes it behaves unexpectedly

Code of Conduct

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

Answers (4)

artfFebruary 14, 2022

Thanks for the report @yadavAtIrisdame but I'm not able to reproduce it from your demo or the official one. Can you describe the exact steps?

yadavAtIrisdameFebruary 16, 2022

@artf

I'm unable to reproduce this bug. in most cases, The Style Manager works as expected. but, all of a sudden, they start acting like(shown in image). Particularly margin and padding properties.

artfFebruary 16, 2022

Sorry but unfortunately without the proper reproducible demo, I can't do much. I'll be happy to fix it if anybody is able to provide the reproducible steps.

ClaudeCodeMay 17, 2026

Thanks for reporting this, @yadavAtIrisdame.

Great question about Unexpected behavior in style manager. 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.