>On Fri, Jul 7, 2017 at 11:54 AM, Jet Villegas <jville...@mozilla.com> wrote: > >> What do we expect to break? > > >I can see that video quality auto adjusment which is based on these APIs >will become malfunction. But, I don't know is this a real use case that a >website implement video quality adjusment based on these APIs.
This will break a number of our internal mochitests. I'm not sure without some checking if the standardized properties can replace them (I think the answer is no in some cases). We could put them behind a pref for testing use. > >> Who's out there using these APIs now? >> > I do believe a number of webrtc services may use these; it's hard to be sure because many of them are not easily findable by searching github or search engines. >There are some addons using these APIs to report media statistics. For our >internal use, there are only some test code using them. And I think the >VideoPlaybackQuality can be used to replace them since it provides a >similar feature. In webrtc and related use, quality is not what these measure; we want to know if frames have arrived or been painted (generally using mozPaintedFrames). There is one test using mozParsedFrames. Before landing any deprecation warnings, you should check with the media/webrtc teams, and we may want to check how one or two external users are using it. -- Randell Jesup, Mozilla Corp remove "news" for personal email _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
