- From: Jonas Sicking <jonas@sicking.cc>
- Date: Mon, 13 Feb 2012 23:39:29 -0500
- To: olli@pettay.fi
- Cc: Anne van Kesteren <annevk@opera.com>, www-dom@w3.org, "Robert O'Callahan" <robert@ocallahan.org>, Stig Halvorsen <stighal@opera.com>
On Wed, Feb 8, 2012 at 7:26 PM, Olli Pettay <Olli.Pettay@helsinki.fi> wrote: > 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. I would imagine that replacing a node is slower in *all* browsers. I agree with Robert, the risk that this will break someone seems very small. The resulting behavior in fact seems nicer for developers in most situations. And the performance benefit seems real, though it would be interesting to see actual numbers for various browsers, which would also help verify my statement above. / Jonas
Received on Tuesday, 14 February 2012 04:40:26 UTC