Issue #6570Opened July 20, 2025by nanto0 reactions

BUG: parser ignores `parser.optionsHtml.keepEmptyTextNodes` option

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chrom v140.0.7307.0 (canary)

Reproducible demo link

https://jsfiddle.net/y3gr69s4/

Describe the bug

How to reproduce the bug?

  1. Create editor instance with parser.optionsHtml.keepEmptyTextNodes option set true.
    const editor = grapesjs.init({
      parser: {
        optionsHtml: {
          keepEmptyTextNodes: true,
        },
      },
    });
    
  2. Load HTML code that contains newlines between elements.
    editor.setComponents('<body>\n<p>foo</p>\n<p>bar</p>\n</body>');
    
  3. Get HTML code.
    const result = editor.getHtml();
    

What is the expected behavior? The resulting HTML code still contains newlines between elements.

<body>
<p>foo</p>
<p>bar</p>
</body>

What is the current behavior? Newlines between elements are stripped from the resulting HTML code.

<body><p>foo</p><p>bar</p></body>

We get the expected result if we set parser.keepEmptyTextNodes option to true but it causes TypeScript type error. I think that keepEmptyTextNodes should be a property of optionsHtml since it is irrelevant to CSS parser.

const editor = grapesjs.init({
  parser: {
    // Error: 'keepEmptyTextNodes' does not exist on type 'ParserConfig'
    keepEmptyTextNodes: true,
  },
});

Code of Conduct

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

Answers (0)

No answers yet.

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.