Re: Optimize setting textContent?

On 02/08/2012 03:47 PM, Anne van Kesteren wrote:
> In https://bugzilla.mozilla.org/show_bug.cgi?id=725221 roc (cc'd, not
> subscribed to the list) suggests optimizing textContent by special
> casing the scenario where the first child is a text node and the string
> being set is non-empty. This would affect mutation observers and makes
> the setting algorithm more complicated, but it is also a performance win
> (in some implementations at least). Opinions?
>
>

Quite horrible special case. APIs should be consistent whenever possible.
innerHTML has the same behavior as textContent. When setting
textContent/innerHTML, all the existing nodes are removed.


-Olli