Re: [dom] Why remove CDataSection? (#142)

Thanks for that link. Reading through that bug, it looks like making it a Text node would have the problem of merging adjacent non-CDATA nodes during normalization. I don't see how serializeAsCDATA would help for that.

Based on what I've read here, I'm working under the assumption that the following will be future-proof:
1. nodeType == 4 (CDATA_SECTION_NODE) is a valid check for CDATA
2. the [CDATA node].data is exactly the contents contained within the original CDATA tags
3. CDATA will not be merged with adjacent text nodes

If any of these assumptions are wrong, please let me know. Even if changing CDATA does not break things now, the chances of things breaking after the next release of FlexJS will be much higher. I believe that E4X will be a very popular feature of FlexJS.

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/142#issuecomment-169262780