Re: Optimize setting textContent? from Olli Pettay on 2012-02-09 (www-dom@w3.org from January to March 2012)

From: Olli Pettay <Olli.Pettay@helsinki.fi>
Date: Thu, 09 Feb 2012 02:26:23 +0200
To: Anne van Kesteren <annevk@opera.com>
CC: www-dom@w3.org, "Robert O'Callahan" <robert@ocallahan.org>, Stig Halvorsen <stighal@opera.com>
Message-ID: <4F3312AF.2000509@helsinki.fi>

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?
>
>

The main problem I have with this is that we would be making API
more inconsistent just because in some implementation(s) optimizing the
inconsistent API might be easier.

We have gone through this same discussion years ago with innerHTML.

Received on Thursday, 9 February 2012 00:27:20 UTC