Component resets attribute values on updating traits ( first time only )
Question
GrapesJS version
- I confirm to use the latest version of GrapesJS
What browser are you using?
Chrome Version 113.0.5672.63
Reproducible demo link
https://jsfiddle.net/rajevar/zLs8q97f/4/
Describe the bug
This is in reference to this discussion https://github.com/GrapesJS/grapesjs/discussions/4759
How to reproduce the bug? https://jsfiddle.net/rajevar/zLs8q97f/4/
- From the blocks, pick Text CAT:Basic component and drag to canvas.
- HTML code after step-1
<div class="text-primary" id="ixci">Insert your text here </div> - Update class attribute for the text component to add a new class. class-a
- HTML code after step-3
<div class="text-primary class-a" id="ixci">Insert your text here </div> - Go to component settings and change id to text-id-1
- HTML code after step-5
<div id="text-id-1" class="text-primary">Insert your text here </div> - In the HTML, class-a got removed from class attribute. This happens for title change as well..
- if the id or title changes again, the class values are preserved.
- Repeat step-3 to add class class-b
- Repeat step-5 to change id to 'text-id-2`
- HTML code after step-10
<div id="text-id-2" class="text-primary class-b">Insert your text here </div>
What is the expected behavior?
Expected html code after step-5 <div id="text-id-1" class="text-primary class-a">Insert your text here </div>
What is the current behavior?
If is necessary to execute some code in order to reproduce the bug, paste it here below: No
Code of Conduct
- I agree to follow this project's Code of Conduct
Answers (3)
sorry, my bad. I wasn't using the latest.
@rajevar I can't reproduce it with the latest version, are you sure you're using the latest one?
Thanks for reporting this, @rajevar.
Great question about component resets attribute values on updating traits ( first time only ). The recommended approach with Canvas 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 #5305
"component:add" event triggers when components are moved
GrapesJS version 0.21.4[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome Version 113.0.5672.63 Reproduc...
Issue #5379
Class modifications of components are not automatically detected
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome Version 116Reproducible demo link htt...
Issue #4497
Updating to GrapesJS v19.5 from v18.4 results in Chrome becoming unresponsive
GrapesJS version[x] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome 104.0.5112.79Reproducible demo link h...
Issue #5245
Contents of component with editable:false are still editable
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome 114.0.5735.198 Reproducible demo li...
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.