W3C home > Mailing lists > Public > whatwg@whatwg.org > November 2009

[whatwg] insertAdjacentHTML

From: Anne van Kesteren <annevk@opera.com>
Date: Tue, 24 Nov 2009 13:29:21 -0200
Message-ID: <op.u3wny7f664w2qv@anne-van-kesterens-macbook.local>
On Tue, 24 Nov 2009 13:24:58 -0200, Daniel Glazman  
<daniel.glazman at disruptive-innovations.com> wrote:
> Anne van Kesteren wrote:
>> The problem is that it is a legacy feature, much like innerHTML.
> That's not a problem. Make insertHTML with the new values and
> make insertAdjacentHTML with the old values just an alias to
> the new ones. Or the contrary. Or whatever. But it's not because
> it's shipped by MS that way that we must stick forever to such
> an horrible definition...

That is actually pretty much how we do it for every feature (consider e.g.  
XMLHttpRequest) because otherwise we have to duplicate too much  
functionality which only increases complexity. I.e. more tests, more APIs  
floating around, more documentation, backwards compatibility issues (new  
duplicate APIs won't work, but the ones they reflect do), etc.

Anne van Kesteren
Received on Tuesday, 24 November 2009 07:29:21 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:19 UTC