Parse5 puts all child nodes of template tags into the content.childNodes property. Our parsing logic used to override Parse5 behavior puts the same child nodes in the childNodes property instead. Due to this discrepancy, the result is a loss of template expressions that are direct children of the template tag because subsequent logic looks for template content under content.childNodes.
Does this pull request introduce a breaking change?
😮💨 No, it does not introduce a breaking change.
Does this pull request introduce an observable change?
Details
Parse5 puts all child nodes of template tags into the
content.childNodesproperty. Our parsing logic used to override Parse5 behavior puts the same child nodes in thechildNodesproperty instead. Due to this discrepancy, the result is a loss of template expressions that are direct children of the template tag because subsequent logic looks for template content undercontent.childNodes.Does this pull request introduce a breaking change?
Does this pull request introduce an observable change?
GUS work item
W-15451162