Issue #3034Opened September 21, 2020by makbari0 reactions

BUG: parse single nodetext as component

Question

Version: current

Are you able to reproduce the bug from the demo?

[X ] Yes [ ] No

What is the expected behavior? The single textnode in any component (e.g. text, cell, ...) should be parsed as a textnode component.

What is the current behavior? Currently, a single textnode in a component is parsed as only a content in htmlParser. When, you call the components method on the child, it returns models as empty array and does not consider textnode as a component.

Are you able to attach screenshots, screencasts or a live demo? In this demo, I some of the cells have only one text node. if you only select two cell in one row and try to merge them, since the models of the component is empty, it returns empty string. single textnode childs should be parsed as a textnode component. in this demo, you can try to merge last row (text1 with text2) and it fails. Demo

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.