Style:property:update and Property onChange trigger excessively
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?
- In the jsfiddle simply click on the "Hello World" component.
- Observe the numerous console logs.
- 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:

Code of Conduct
- I agree to follow this project's Code of Conduct
Answers (3)
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)
}
});
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.
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:
- Check the GrapesJS documentation for your specific module
- Look for the
on()event listener method - 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.
Issue #4576
Clicking 'wrap for style' button affects the inner components of other components inside the same text box
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome 104.0.5112.101 Reproducible demo link...
Issue #6706
TypeError: e.getRoot is not a function (Race condition in Style Manager)
GrapesJS version [x] I confirm to use the latest version of GrapesJS What browser are you using? All browsers (Chrome, Safari, Firefox, Edg...
Issue #4350
Style Manager don't update background when component is selected
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Brave Browser V1.39.111 Reproducible demo...
Issue #5990
When you delete a component, duplicate classes between components will be deleted.
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome 126.0.6478.127(Windows) Reproducibl...
Paid Plugins That Match This Issue
Curated by issue keywords and label relevance to help you ship faster.
Loading paid plugin recommendations...
Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.
Browse free plugins →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.
Tutorial
Find the Right GrapesJS Plugin in Seconds: Smarter Discovery Is Live
We're shipping a set of discovery upgrades. New label filters, a proper compatibility switch for GrapesJS vs Studio, one-click and a smarter sort bar.
Tutorial
GrapesJS vs Webflow vs Tilda: What to Choose for Your Business in 2026
Choosing the right website platform in 2026 is no longer just about building a site
Tutorial
GJS Market 2.0 - Donations, Tracking, Labels and Better Product Discovery
We’ve rolled out a new set of GrapesJS marketplace updates across GJS Market, focused on improving how creators distribute products
Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.