Issue #3655💬 AnsweredOpened July 30, 2021by TRIGGEREDcoder0 reactions

The form button name changes are not getting captured in generated html code

Quick answerby artf

Hi @TRIGGEREDcoder there is an issue with the preset webpage plugin which references the old form plugin containing the bug. So, I'm closing this one as it's not part of the core and will update the plugin reference soon.

Read full answer below ↓

Question

Version: Version 0.17.19(grapesjs) Version 0.1.11(grapesjs-preset-webpage)

Are you able to reproduce the bug from the demo?

  • No

What is the expected behavior? If I change a button name by changing the text in Component Settings for the button. The change should reflect in the Canvas as well as the html code in code view.

Describe the bug detailed I drag a form component on the canvas. Select the button tab, go to component settings. chose the button type and change the text. The button text changes on the screen and the button type also changes on the view code html but the button name is nowhere reflecting at all.

What is the current behavior? The button label changed is no where reflecting in the html code.

Are you able to attach screenshots, screencasts or a live demo?

  • Yes (attach) As on codebox, grapesjs-preset-webpage plugin is not getting imported, I am not able to create a demo but I will share some screenshot from the actual grapesjs canvas where I am developing. In the first, I have shown the component settings. In the second picture, I have shown the html code generated from view code, where both the buttons are labelled as Send. image image

Answers (2)

artfAugust 2, 2021

Hi @TRIGGEREDcoder there is an issue with the preset webpage plugin which references the old form plugin containing the bug. So, I'm closing this one as it's not part of the core and will update the plugin reference soon.

ClaudeCodeMay 17, 2026

Thanks for reporting this, @TRIGGEREDcoder.

The issue with The form button name changes are not getting captured in generated html code appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifications overlap, creating an inconsistent state.

What to try:

  1. Add a setTimeout wrapper to ensure the DOM has settled:
setTimeout(() => {
  // your operation here
}, 0);
  1. Check initialization order — make sure components are fully loaded before you interact with them

  2. Use the editor's event system — listen to completion events:

editor.on('component:mount', (component) => {
  // safe to interact with component here
});

Recommended next steps:

  • Test with the latest GrapesJS version if you haven't
  • Provide a minimal reproducible example (CodeSandbox) — this helps the team identify the root cause faster
  • Include GrapesJS version, browser, and console errors in your report

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.