Re: Strawman Promises consensus position, based on Thursday's telechat

On Tue, Oct 7, 2014 at 5:31 PM, Adam Roach <> wrote:
> That's pretty tone-deaf when you consider the implications for new
> implementations.

If existing deployment is indeed so problematic you could always
include the deprecation warning in the specification:

It would indeed be bad if new implementations felt themselves forced
to reverse engineer existing implementations. However, it does seem
problematic to define a new method name that nobody has implemented
yet hoping everyone has a shim in place. I'm not sure why e.g. Blink
or Gecko would unprefix getUserMedia() if that is not the API we would
like to end up with anyway.

Given this you should probably just define moz/webkitGetUserMedia() or
some such and encourage everyone to move away from it, stating it will
be removed in 2016-2017.


Received on Tuesday, 7 October 2014 15:46:23 UTC