Issue #3457✓ SolvedOpened May 13, 2021by RaresVlaiduc3 reactions

Custom trait input not working

Quick answerby artf2

@RaresVlaiduc mmm I'd expect it to work also with an HTML string... I have to check it

Read full answer below ↓

Question

Hi @artf !

Version: 0.17.3

Are you able to reproduce the bug from the demo?

  • Yes
  • No

What is the expected behavior?

The input is created correctly

Describe the bug detailed

I am trying to create a custom input (checkbox) and it doesn't work.

What is the current behavior?

See attach.

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

  • Yes (attach)
  • No

Code: image

Result: image

The area that should be some kind of "input" is not clickable.

If I am doing something wrong, let me know :)

Answers (4)

👍 Most helpfulartfMay 18, 2021

@RaresVlaiduc mmm I'd expect it to work also with an HTML string... I have to check it

ahmedderkaouiMay 17, 2021

Then, in createInput() you should return an Element. So instead of returning a simple string, do this:

const el = document.createElement('div');
el.innerHTML = `<input type='checkbox'/>`
return el;
ahmedderkaouiMay 17, 2021

If you want to have a simple checkbox with label, no need to create custom trait, you can just use directly:

editor.DomComponents.addType('text', {
            model: {
              defaults: {
                traits: [
                  {type: 'checkbox', label: 'Fix position when scrolling', name: 'position-sticky'}
                ]
              }
            },
});
ClaudeCodeMay 17, 2026

Thanks for reporting this, @RaresVlaiduc.

The issue with Custom trait input not working 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.