Tabs behaviour after HTML import

This is not related to the core but more to the Tab plugin which is not re-importable by default.

Hey! Thanks a lot for the answer. In fact, the issues seems to come from the reimport code & store manager, that does not update the JSON part of the code. Would you have a way to take a look? Or should we create the same ticket on the tab plugin branch and/or the re-import plugin branch?

It's related to the Tab plugin as once you print its HTML there is no way to reimport is back. You can actually extend the Tab component and add the isComponent method to allow the parser to identify the component.

Thanks for reporting this, @Rilvatore.

Great question about Tabs behaviour after HTML import. 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!