Issue #4601💬 AnsweredOpened September 21, 2022by bit-ocean1 reactions

Update() of custom types added to StyleManager is no more triggered when switching between some targets.

Quick answerby ronaldohoch1

Same as described here, not a issue: https://github.com/artf/grapesjs/issues/4350

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chromium 104

Reproducible demo link

https://jsfiddle.net/aw8p0h9j/

Describe the bug

How to reproduce the bug?

  1. Open the jsfiddle link.
  2. Click between the divs, then between any of divs and the background.

What is the expected behavior? In older versions of grapesjs (0.17.26), the update is triggered and console logs the clicks, the code of update() is executed.

What is the current behavior? In the version 0.20.1 of grapesjs, the update is not triggered when switching between different targets at least when 1. no property value on component, 2. value on components is the same, ...

JS:

const editor = grapesjs.init({
	container: '#gjs',
  fromElement: 1,
  height: '100%',
  styleManager: {},
  storageManager: { type: 0 },
  plugins: ['gjs-blocks-basic', ]
});

  const sm = editor.StyleManager;

  sm.addType('newinput', {
     // Create UI
     create({ props, change }) {
       const el = document.createElement('div');
       el.innerHTML = '<input class="my-input" />';
       const inputEl = el.querySelector('.my-input');
       inputEl.addEventListener('change', event => change({ event }));
       inputEl.addEventListener('input', event => change({ event, partial: true }));
       return el;
     },
     // Propagate UI changes up to the targets
     emit({ props, updateStyle }, { event, partial }) {
       console.log("Change in value.");
     },
     // Update UI (eg. when the target is changed)
     update({ value, el }) {
       console.log("Target changed", Date.now());
     },
     // Clean the memory from side effects if necessary (eg. global event listeners, etc.)
     destroy() {}
  })

  // Add new sector
  const newSector = sm.addSector('sector-id', {
    name: 'New sector',
    open: true,
    properties: [
    	{
      	name: "Custom property",
        type: "newinput",
        property: "padding",
      }
    ],
  });

HTML:

<div id="gjs">
  <div style="padding: 25px">Logs appear only when clicking between body and any of divs, but not between divs.</div>
  <div style="padding: 25px">As long the divs have the same value of padding there is no log while clicking between them.</div>
</div>

Is this intended breaking change or a bug?

Code of Conduct

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

Answers (4)

artfSeptember 22, 2022

Yeah but even in a case of a custom UI, the update is skipped if the value is not changed as it's not necessary.

bit-oceanSeptember 22, 2022

The code that I pasted is using the standard api, pretty much copy/paste from the documentation. And clearly the update's mechanism has changed between the versions.

Before if target element had been changed, the update was triggered, and we could run code that under certain conditions re-renders the component. @artf what would be your proposal of best strategy to replace it now? Should I add a custom listener to target change event rather? What is your recommendation of implementation that's gonna ensure more compatibility with staying up to date with core changes of grapesjs?

In short, I need to be able, when target is changed, to call a callable and both get and set the value of the custom type input.

ClaudeCodeMay 17, 2026

Thanks for reporting this, @bit-ocean.

Great question about update() of custom types added to StyleManager is no more triggered when switching between some targets.. 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.