Issue #4732Opened November 17, 2022by Rilvatore0 reactions

BUG: Tabs behaviour after HTML import

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome 107 (MacOS)

Reproducible demo link

https://grapesjs.com/demo.html

Describe the bug

How to reproduce the bug?

  1. Drag and drop the Tabs block into the editor content
  2. Click on the "import" button on the top
  3. Change something in the html content (rename one of the previous tabs created for example)
  4. Click on "import"

What is the expected behavior? The tabs have to be editable (add new tab and navigate between them) after html import

What is the current behavior? The tabs have not the "tab" type anymore and can't be edited

Before html import: Capture d’écran 2022-11-17 à 10 50 41

After html import: Capture d’écran 2022-11-17 à 10 51 04

Thank you for your help!

Code of Conduct

  • I agree to follow this project's Code of Conduct

Answers (3)

artfNovember 17, 20220 reactions

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

RilvatoreNovember 18, 20220 reactions

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?

artfNovember 18, 20220 reactions

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.

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...

Browse Plugin Categories

Jump directly to plugin category pages on the marketplace.