Should the sanitizer normalize

[annevk]

See #202 for context. Someone(tm) should probably look at what ranges do as they have similar multi-node mutation operations.

[otherdaniel]

Ranges apparently don't normalize, or at least Range.insertNode doesn't.

spec: https://dom.spec.whatwg.org/#concept-range-insert

impl:

d = document.createElement("div");
d.textContent = "abcdef";
d.childNodes.length   // 1, as expected

r = document.createRange();
r.setStart(d.firstChild, 3);  // position range in the middle of the text node.
r.insertNode(document.createTextNode("XXX"));
d.innerHTML  // "abcXXXdef"
d.childNodes.length  // 3

[mozfreddyb]

I just can't really think of any pros & cons. In case of setHTML(), when starting with a string, I don't think there's particular need to preserve adjacent text nodes as individual items and combining them could save a bit of memory, maybe.

On the other hand, doing a full normalization pass after or during sanitization is a bit of extra work that just not be necessary.

I don't have strong feelings either way. From what I can tell, there is no other API really normalizing. Given this, I can't think of a reason why this one should.

[annevk]

@smaug---- @rniwa thoughts?

[smaug----]

My initial feeling is that normalization would be just a bit odd, even unexpected size effect here, given that other APIs don't tend to normalize.

[mozfreddyb]

Without anyone being of a strong opinion and the web platform mostly not normalizing, we will also just not normalize.

[mozfreddyb]

I guess this is resolved and does not need any further action.