StylePrefix property not overiding the gjs in most elements with the gjs-class
Thanks for reporting this, @JonathanRiche. Great question about stylePrefix property not overiding the gjs in most elements with the gjs-class. The recommended approach with StyleManager is to use the event-driven API. Start here: Check the GrapesJS documentation for your specific module Look for the on() event listen...
Read full answer below ↓Question
GrapesJS version
- I confirm to use the latest version of GrapesJS
What browser are you using?
Version 107.0.5304.107 (Official Build) (64-bit)
Reproducible demo link
https://jsfiddle.net/jonrobert/2gLdur9c/3/
Describe the bug
How to reproduce the bug?
- Modify the stylePrefix property on any of the options in the config option when running the grapesjs.init() function ie
layerManager:{
stylePrefix:'customStylePrefix'
},
blockManager: {
stylePrefix:'customStylePrefix'
}
What is the expected behavior? Expected behaviour is for the .gjs-classes are replaced with the stylePrefix like previous versions of grapesJs
What is the current behavior? Current behaviour is the stylePrefix property is not being applied even when setting in the config
If is necessary to execute some code in order to reproduce the bug, paste it here below:
const editor = grapesjs.init({
//stylePrefix:'customStylePrefix',
container: '#gjs',
fromElement: 1,
height: '100%',
storageManager: { type: 0 },
plugins: ['gjs-blocks-basic'],
layerManager:{
stylePrefix:'customStylePrefix'
},
blockManager: {
stylePrefix:'customStylePrefix'
}
});
Code of Conduct
- I agree to follow this project's Code of Conduct
Answers (1)
Thanks for reporting this, @JonathanRiche.
Great question about stylePrefix property not overiding the gjs in most elements with the gjs-class. The recommended approach with StyleManager 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 #4752
Component with pointer-events: 'all' (except wrapper) or editable component are draggable & droppable to itself.
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome 107.0.5304.121 (Official Build) (arm6...
Issue #6659
Symbol styles not synced
GrapesJS version [x] I confirm to use the latest version of GrapesJS What browser are you using? Firefox 145.0 (64-bit) Reproducible demo l...
Issue #4897
component:styleUpdate / component:styleUpdate:propertyName not fired
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Edge 109.0.1518.70 Reproducible demo link...
Issue #6515
Resizing an element affects all elements with the same class
GrapesJS version [x] I confirm to use the latest version of GrapesJS What browser are you using? Chrome 136.0.7103.93 Reproducible demo lin...
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 →Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.