W3C home > Mailing lists > Public > public-webrtc@w3.org > March 2014

Re: Question about mandatory API in webrtc and mediacapture specs.

From: Harald Alvestrand <harald@alvestrand.no>
Date: Thu, 13 Mar 2014 10:59:50 +0100
Message-ID: <53218196.9040801@alvestrand.no>
To: public-webrtc@w3.org
On 01/28/2014 03:05 PM, Kiran Kumar wrote:
> Dear All,
> Is there any plan to specification or wiki page to know which API's of 
> webrtc and mediacapture specs are mandatory to implement in a browser 
> and which of those are optional.
> Thanks,
> Kiran.
Having finally caught up on this thread, and with apologies for not 
responding earlier:

Short version: No. This is not part of the specification, should not be, 
and will not be.

The W3C way of working is that one puts the specifications into a spec.
You implement all of the API. Some of the API may return "not possible 
to do this" because the underlying platform/implementation doesn't 
support it - but you assume that browsers will implement all of the API.

If, after a while, browsers don't implement certain features, they get 
removed from the spec. (in theory, at least).

Browsers won't implement all of an API in one go. For each browser, it 
makes sense to have lists of what they have implemented, what they have 
stubbed out (works but returns "not possible"), and what's missing. But 
keeping a central list of recommendations makes no sense; it's each 
browser's business.

Missing API calls can be probed for. But they need to be treated as 
bugs, not features.

Received on Thursday, 13 March 2014 10:00:19 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:38 UTC