Issue #4859πŸ’¬ AnsweredOpened January 20, 2023by zoilorys0 reactions

Editing CSS property sets a style to a common class instead of element

Quick answerby artf

You just need to enable this option: https://grapesjs.com/docs/modules/Selectors.html#component-first-selectors

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome v108

Reproducible demo link

https://grapesjs.com/demo.html

Describe the bug

How to reproduce the bug?

  1. Setup grapesjs editor
  2. Import following template https://pastebin.com/d9S2M0iS
  3. At the very bottom of the template you will see wrapped facebook button
  4. Select table cell it is in, and try t change its width

What is the expected behavior? When style property of the element is edited - styles should be updated only on selected element.

What is the current behavior? Changing width of the cell for some reason edits common class in this template, which is applied to other elements as well, causing unexpected behavior (see video) . This I couldn't reproduce on the demo setup, and cant provide our exact setup to the public, but maybe you have ideas why this might be happening.

https://user-images.githubusercontent.com/12827614/213744169-cdf4c9cb-0ad0-4d2c-8e19-ef1e6ff1937e.mp4

Code of Conduct

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

Answers (2)

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @zoilorys.

Great question about Editing CSS property sets a style to a common class instead of element. The recommended approach with StyleManager 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.