Re: Overload of Dictionary and Callback - why is this disallowed? from Boris Zbarsky on 2015-12-02 (public-script-coord@w3.org from October to December 2015)

From: Boris Zbarsky <bzbarsky@mit.edu>
Date: Wed, 2 Dec 2015 10:34:10 -0500
To: public-script-coord@w3.org
Message-ID: <565F0F72.5010702@mit.edu>

On 12/2/15 7:59 AM, Harald Alvestrand wrote:
> The spec's IDL has changed multiple times over the years.

Ah, this is the continuing webrtc story, ok.  ;)

> void createOffer (RTCSessionDescriptionCallback successCallback,
> optional RTCPeerConnectionErrorCallback failureCallback, optional
> MediaConstraints constraints);

OK.  So this is a Chrome-local problem, not a problem for the spec, 
right?  Certainly Gecko implements the current spec, not the August 2012 
thing.

Given that it's Chrome-local, and the solution is only needed 
temporarily if Chrome plans to align with the spec at all, it seems like 
it can be solved in any way acceptable to the Chrome team (e.g. by 
temporarily changing their IDL compiler to allow such overloads, either 
in general or for some whitelist of APIs).

-Boris

Received on Wednesday, 2 December 2015 15:34:42 UTC