Deleting a component without deleting its corresponding style, will adding new components later cause style conflicts?

it‘s still a problem

I don't see how this is a core bug. You're using your own copy/paste logic and it doesn't even seem correct, you should take care of the unique ids of each component/rule.

After deleting these child components, their styles still remain.

If you're copying all matched styles it would also contain styles used by other elements so you can't simply expect those styles to be deleted.

Please, if you're submitting a bug, ALWAYS provide a reproducible demo.

Thanks for reporting this, @pittleCheung.

Great question about Deleting a component without deleting its corresponding style, will adding new components later cause style conflicts?. 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!