Issue #3778πŸ’¬ AnsweredOpened September 15, 2021by codingmachine161 reactions

Select options are not displaying - new anomaly

Quick answerby Bran72❀ 1

Hi ! I also have your issue since the v.0.17.25. I think it will be fixed in the next release. So the temporary solution is to downgrade to v0.17.22... Hope it will help you !

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://github.com/artf/grapesjs/issues/3735

Describe the bug

I am have issue related to select box . It is showing issues as in console

[Traits]: 'select' type not found {level: 'warning'}

When we drag component and click on the element on which traits are set , it shows input text instead of select box. On the other hand, after component drag, if we click on any other element and then click on that element which has traits then select box will display. very strange!

Note: This issue is mentioned here https://github.com/artf/grapesjs/issues/3735 . Author updated two files and reported as fix but it is not fix in accordance with above scenario.

Code of Conduct

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

Answers (4)

Bran72β€’ September 16, 2021

Hi ! I also have your issue since the v.0.17.25. I think it will be fixed in the next release.

So the temporary solution is to downgrade to v0.17.22... Hope it will help you !

artfβ€’ September 16, 2021

Correct, it's been fixed here #3735

codingmachine16β€’ September 16, 2021

OK . Sure. Thanks. For information, this issue does not exist on 0.17.22 but it is in 0.17.25

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @codingmachine16.

The issue with Select options are not displaying - new anomaly 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.