Contenteditable attribute on Layer's name span
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)
If you double click on the layer name you can actually change its name :)
@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.
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.
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:
- Check the GrapesJS documentation for your specific module
- Look for the
on()event listener method - 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.
Issue #3600
[Question]: Event listener to visibility(eye) icon in the Layer Manager
I would like to listen to the eye icon in the layer manager from the editor, based on which, I need to write the custom styles. Is there an...
Issue #3250
Question : Layer labels
@artf I am loving working with GJS. I have one last thing I'd love your help on. It would be incredibly helpful to be able to customise the...
Issue #3367
Modal template
Is there a way for me to modify the template from a compiled state? https://github.com/artf/grapesjs/blob/d3256e621bb43a537213ffcd86b10dc0b...
Issue #3721
Test drag and drop with Cypress
Hi @artf. I would like to run some test scenarios on GrapesJs using Cypress tool. However i am unable to simulate drag and drop mode using...
Paid Plugins That Match This Issue
Curated by issue keywords and label relevance to help you ship faster.
Loading paid plugin recommendations...
Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.
Browse free plugins →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.
Tutorial
How to Build a Production GrapesJS Editor: The Complete Walkthrough of Brief, Preset, Plugins, and Services
A complete walkthrough of building a production GrapesJS editor: how to choose a preset, pick plugins, and scope setup services without burning a sprint.
Tutorial
Big Updates: TinyMCE 8 and Placeholder 2.0 for GrapesJS
In May we shipped major updates to two of our most popular GrapesJS plugins — TinyMCE Inline Text Editor and Placeholder.
Tutorial
Find the Right GrapesJS Plugin in Seconds: Smarter Discovery Is Live
We're shipping a set of discovery upgrades. New label filters, a proper compatibility switch for GrapesJS vs Studio, one-click and a smarter sort bar.
Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.