13046 2011-06-24 12:32:21 +0000 Should we get rid of replaceWholeText? 2011-09-20 08:48:58 +0000 1 1 1 Unclassified WebAppsWG DOM unspecified All All RESOLVED FIXED CORE-41309 P2 normal --- 1 Ms2ger annevk annevk ayg bugs ian jonas mike www-dom public-webapps-bugzilla oldest_to_newest 50231 0 Ms2ger 2011-06-24 12:32:21 +0000 50281 1 jonas 2011-06-24 20:31:56 +0000 Yes! As far as I know no good use cases have ever been presented. 50308 2 annevk 2011-06-25 10:02:37 +0000 Apparently Acid3 uses replaceWholeText(). 50309 3 annevk 2011-06-25 10:03:40 +0000 Only once though and should be easy to remove. 56103 4 annevk 2011-08-31 13:12:14 +0000 https://bugzilla.mozilla.org/show_bug.cgi?id=683482 56108 5 bugs 2011-08-31 13:53:16 +0000 replaceWholeText makes certain DOM modifications faster. If you have <span>[text1][text2][text3]</span> using [textX].replaceWholeText(foo) should be faster than span.textContent = foo; or span.innerHTML = foo; Or manually removing all but one text node. But I'm not sure if that is a case to worry about. (In any case http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#dom-text-replacewholetext is buggy, since based on it all the adjacent text nodes should be removed, but that is not what replaceWholeText does.) 56464 6 annevk 2011-09-07 13:08:22 +0000 I fixed the description of replaceWholeText for now. Hopefully we can remove it though. I do not think performance matters that much here. 57023 7 annevk 2011-09-20 08:48:58 +0000 Gone: https://bitbucket.org/ms2ger/dom-core/changeset/2f0511729bf5