Issue #3365💬 AnsweredOpened March 26, 2021by Franci5co5aoco0 reactions

Contenteditable attribute on Layer's name span

快速解答by artf

If you double click on the layer name you can actually change its name :)

Read full answer below ↓

Question

Hi @artf

I would like to know why layer's name span has a contenteditable attribute.

There is no mechanism implemented on grapesJs to really change the layer name after refreshing the page if I'm not wrong. It can be a little bit confusing to the user.

<div class="gjs-layer-title-inn">
  <i class="gjs-layer-caret fa fa-chevron-right" data-toggle-open=""></i>
  <span class="gjs-layer-name gjs-no-app gjs-layer-name--no-edit" data-name="" contenteditable="true">Image</span>
</div>

Thanks.

Answers (4)

artfApril 7, 2021

If you double click on the layer name you can actually change its name :)

Franci5co5aocoApril 7, 2021

@artf , sorry I think I was misunderstood. I meant you can change the name but when you refresh the page the changes are not been saved... and I think that there isn't a mechanism implemented to achieve it.

When the user modifies the layer name, he expects that this modification be saved, but it's not the case.

Here a little video showing the case using the official GrapesJs demo: I changed theHeader layer's name toTest when refreshing the page Header stills the name of the layer. Is it the expected behaviour? If yes, why It has an contenteditable attribute?

Thanks a lot for your time.

https://user-images.githubusercontent.com/23215166/113898126-dacdae80-97cb-11eb-9224-1d57d2d53195.mov

artfApril 20, 2021

No, the mechanism to store/load custom layer names is there, the only issue is that the change is not triggering the store... indeed, if you try to move some component right after the change, you will see them after page refresh. Anyway, this should be fixed with the upcoming page manager module.

ClaudeCodeMay 17, 2026

Thanks for reporting this, @Franci5co5aoco.

Great question about contenteditable attribute on Layer's name span. The recommended approach with GrapesJS 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.