Artur Arseniev

Hi Juan, thanks for the report, yeah actually `createInput` requires you to return an HTML string or HTMLElement. I think it's good to have errors in cases like that but...

@JonyBlade ok, why not

We should apply the same logic from https://github.com/artf/grapesjs/blob/201e1f9a61783080f7be885e9e0be9a40ecc16cc/src/code_manager/model/CssGenerator.js#L151-L162 here https://github.com/artf/grapesjs/blob/201e1f9a61783080f7be885e9e0be9a40ecc16cc/src/css_composer/view/CssRulesView.js#L122-L129

Currently, the editor imports only the content inside the body. To make it understand also other document nodes, it'd require a refactor of the [current HTML parser](https://github.com/artf/grapesjs/blob/dev/src/parser/model/ParserHtml.js)

> can we expect this feature to be in next version? I'm not sure, but I'm gonna try

Hi @RuslanShokhanov currently I have no ETA for this feature and not planning to do it soon

@wimurk you have to remove them manually right now

Create a live demo, please

I think, currently, it's not easy to achieve it. The Sorter module is quite old and messy and I'd need to refactor it in order to allow such functionality (which,...

Does anyone is able to create a reproducible demo, please?