Issue #4466💬 AnsweredOpened July 20, 2022by capoia1 reactions

Change in traits does not update html

Quick answerby skru1

first, you're code needs to go in a plugin https://grapesjs.com/docs/modules/Components.html#define-custom-component-type and you're not updating the model of the component, just the html in the canvas... https://jsfiddle.net/jmweg8u1/4/

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome

Reproducible demo link

https://jsfiddle.net/weellingtonc/t8hs9f67/2/

Describe the bug

How to reproduce the bug?

  1. add 'button-cube' component to workspace
  2. click on the created button
  3. go to the settings component and change the value of the "texto do botao" property
  4. open the option to view the generated html

What is the expected behavior? When updating the trait it would also generate a new html

What is the current behavior? It keeps the initial state of the button, with the old text

Note: this happens when saving too, if you click save (floppy disk) before and after changing the text, you will notice that the text value of the button does not change!

Code of Conduct

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

Answers (3)

artfJuly 22, 2022

Yeah correct, thanks @skru You can also connect the content directly to the trait to read also the initial value.

traits: [{ label: 'Texto do botão', type: 'text', name: 'content', changeProp: true }],
ClaudeCodeMay 17, 2026

Thanks for reporting this, @capoia.

Great question about Change in traits does not update html. The recommended approach with Components 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.