You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apparently, per tests and browser behavior, this includes both Text and CDATASection nodes. While I might say that both are "text nodes", the current spec's typography of "Text node" is a bit misleading, implying it would not include CDATA section nodes.
I'd like to suggest that the spec try to be as clear as possible and use either "text node" or (better) "inclusive text node" when referring to both Text and CDATASection nodes.
Via jsdom/jsdom#2441, where @Zirro remarks that we might not have test coverage for very many other places in the spec that have this problem.
The text was updated successfully, but these errors were encountered:
I would really rather not block on that, especially since I consider it a dubious and over-formal solution. We don't need all that machinery just to change "Text node" to "Text or CDATASection node" or similar.
https://dom.spec.whatwg.org/commit-snapshots/23ec6421f47ab629bd14dfc6d4910414dc443d0b/#mutation-algorithms
Apparently, per tests and browser behavior, this includes both
Text
andCDATASection
nodes. While I might say that both are "text nodes", the current spec's typography of "Text
node" is a bit misleading, implying it would not include CDATA section nodes.I'd like to suggest that the spec try to be as clear as possible and use either "text node" or (better) "inclusive text node" when referring to both
Text
andCDATASection
nodes.Via jsdom/jsdom#2441, where @Zirro remarks that we might not have test coverage for very many other places in the spec that have this problem.
The text was updated successfully, but these errors were encountered: