Issue #5086💬 AnsweredOpened May 2, 2023by SagarMaria0 reactions

Style:property:update and Property onChange trigger excessively

Quick answerby artf

The behaviour is correct as style:property:update triggers on any update of the Style Manager Property (not only its value). So for your specific case you would need to update the callback in this way

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome Version 112.0.5615.137 (Official Build)

Reproducible demo link

https://jsfiddle.net/SagarMaria/sunygp2f/3/

Describe the bug

How to reproduce the bug?

  1. In the jsfiddle simply click on the "Hello World" component.
  2. Observe the numerous console logs.
  3. Click away elsewhere on the canvas, repeat.

What is the expected behavior? style:property:update should only trigger on some style property change for the selected component

What is the current behavior? style:property:update event is instead firing numerous times even when a component is simply selected

If is necessary to execute some code in order to reproduce the bug, paste it here below:

// editor.on(
      'style:property:update',
      (property) => {
        console.log('property', property);
      },
    );

I'm looking for a way to target a the radio input change event on a custom sector in style manager. Existing documented methods don't seem to be reliable as they are firing in undesired ways.

Ideally I would like some event to detect a change in this radio button value for text align, and be able to utilize that event to add certain class names to the component, look for parents, etc: image

Code of Conduct

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

Answers (3)

artfMay 2, 2023

The behaviour is correct as style:property:update triggers on any update of the Style Manager Property (not only its value). So for your specific case you would need to update the callback in this way

editor.on('style:property:update', ({ property, to }) => {
  // Check for the property name and if the update is related to the value
  if (property.getName() === 'text-align' && to.value !== undefined) {
     console.log('text align property updated with', to.value)
  }
});
SagarMariaMay 2, 2023

Hi @artf, thanks for the quick reply, but actually, part of the problem is still that even after making a change e.g. click "center" align radio option with the if statement you suggested, subsequent selections of that component still log out style:property:update value with property and to set as the existing value (even if you don't change anything and just select the component). Here is a quick video below and I also updated the jsfiddle with your suggestion.

Is there a way to simply listen for a change on the radio value/click on a different radio option in the style manager? I also tried using the property's onChange but it operates in a similar way to the style:property:update, logging with each click even if no style value has been updated.

https://user-images.githubusercontent.com/83087753/235668944-27e9ee52-f24f-412f-9707-c63cef4b502e.mp4

ClaudeCodeMay 17, 2026

Thanks for reporting this, @SagarMaria.

Great question about Style:property:update and Property onChange trigger excessively. 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.