[Bug 27386] Removing createCDATASection() unlikely to be successful

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27386

--- Comment #7 from Philip Jägenstedt <philipj@opera.com> ---
AFAICT, these are the ways that CDATASection is observable in Blink:

1. The CDATASection interface itself
2. CDATASection.nodeName is "#cdata-section"
3. CDATASection.nodeType is 4 (CDATA_SECTION_NODE)
4. Document.createCDATASection()
5. The XML parser can create CDATASection
6. XMLSerializer.serializeToString() can serialize CDATASection

I could add counters for 2, 3, 5 and 6 (1 is hard to count and 4 already
counted) but even if the usage is high it could still be safe to remove if
people are just iterating over documents and dispatching based on nodeType, for
example.

Would counters for the above or anything else be worthwhile adding?

Is there a spec for XML parsing that we should have changed if we try changing
the parser to output Text nodes instead of CDATASection?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 25 November 2014 22:45:42 UTC