- From: Cameron McCormack <cam@mcc.id.au>
- Date: Tue, 06 Dec 2011 16:14:36 +1100
- To: Anne van Kesteren <annevk@opera.com>
- CC: "public-script-coord@w3.org" <public-script-coord@w3.org>, Travis Leithead <travis.leithead@microsoft.com>
On 22/10/11 12:07 PM, Anne van Kesteren wrote: > Well, I mentioned XMLHttpRequest's send() method. The example that came > up on www-dom was about overloading appendChild() or append() (proposal) > to make Text node creation easier. I do not know any other places that > overload a method with both DOMString and an object. If we proceed with changing the overload resolution algorithm as proposed in the other thread, then I think we should drop [AllowAny] and then you can just rely on the ordering of the operations on the interface to influence which overload is chosen when a non-matching type is passed. WDYT?
Received on Tuesday, 6 December 2011 05:15:16 UTC