Issue #6039✓ SolvedOpened August 6, 2024by Gryphonn3 reactions

Cannot set Block display value

Quick answerby artf2

Yeah, the issue is here: https://github.com/GrapesJS/grapesjs/blob/1e3766f0060e6da502fccf9ba9eb938d5ac860bb/src/style_manager/model/PropertyFactory.ts#L267 Would it make sense to add a new option like initial and make it the default one?

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome 126

Reproducible demo link

https://jsfiddle.net/Gryphonn/ob1pznh6/

Describe the bug

How to reproduce the bug?

  1. Select any word.
  2. Wrap it for style.
  3. Keep this word selected.
  4. Go to General -> Display
  5. I want Block. I click Block but nothing happens.

What is the expected behavior? Display value must be either empty so that I can instantly choose whatever I need. Or it must show the current actual display value of the selected text. Which is Inline in this case and not Block.

What is the current behavior? Currently I need to click twice. First, click anything except Block. The display field is activated. Then I should click Block.

If is necessary to execute some code in order to reproduce the bug, paste it here below:

// your code here

Code of Conduct

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

Answers (4)

danstarnsAugust 8, 2024

Hi @Gryphonn, I tried to reproduce your issue but the steps aren't that clear, please rephrase.

bandicam.2024-08-08.21-07-14-667.mp4

Thank you for a detailed report 🙏

It looks like we should better handle the default display so you don't have to first change to another display and back again.

danstarnsAugust 8, 2024

Hi @Gryphonn,

I tried to reproduce your issue but the steps aren't that clear, please rephrase.

ClaudeCodeMay 17, 2026

Thanks for reporting this, @Gryphonn.

Great question about Cannot set Block display value. The recommended approach with StyleManager is to use the event-driven API.

Start here:

  1. Check the GrapesJS documentation for your specific module
  2. Look for the on() event listener method
  3. 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.

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.