Issue #3763πŸ’¬ AnsweredOpened Sep 10, 2021by abolabo0 reactions

V0.17.25 . Trait button in the custom component defining.

Quick answerby artf

Thanks @abolabo for the report, this issue was actually already fixed here #3735

Read full answer below ↓

Question

GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? FirefoxReproducible demo link https://jsfiddle.net/abolabo/3g7j519h/19/Describe the bug Code works incorrect: traits: [ { type: "button", text: "click me", full: true, command: (editor) => console.log("trait command"), }, ], I expecting <button> tag but input type=button shows instead. No text inside button. No command run.Code of Conduct[X] I agree to follow this project's Code of Conduct

Answers (2)

artfβ€’ Sep 11, 2021

Thanks @abolabo for the report, this issue was actually already fixed here #3735

GJSBlockβ€’ May 17, 2026

Thanks for reporting this, @abolabo. The issue with v0.17.25 . Trait button in the custom component defining. 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...

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.