Closed ronaldohoch closed 2 years ago
Hi @ronaldohoch thanks for the report. What you're saying is true, but unfortunately, this is the parsing result of the native HTML DomParser, so I don't see any proper way to fix it.
const parser = new DOMParser();
console.log(parser.parseFromString(`<noscript><img/></noscript>`, 'text/html'));
// You will see how it'll put <noscript> inside the <head> and <img> inside the <body>
The only workaround for cases like this (importing an HTML string containing tags like noscript) is to force the parser to see the content inside the body.
editor.addComponents(`<body><noscript><img /></noscript></body>`);
GrapesJS version
What browser are you using?
Brave Versão 1.32.106 Chromium: 96.0.4664.45 (Versão oficial) 64 bits
Reproducible demo link
https://jsfiddle.net/960huLz5/
Describe the bug
How to reproduce the bug?
editor.addComponents('<noscript><img src=""></noscript>');
What is the expected behavior? Image should stay inside noscript's tag
What is the current behavior? Image don't stay inside noscript tag
If is necessary to execute some code in order to reproduce the bug, paste it here below:
Here what the parseHtml returns: It's used in facebook pixel script:
And i can't find a way to update the component to accept to be droppabble inside noscript tag https://github.com/artf/grapesjs/blob/dev/src/dom_components/model/ComponentImage.js
Code of Conduct