Re: Intent to unship: moz*Frames attributes of HTMLVideoElement

>On Monday, July 10, 2017 at 3:28:07 PM UTC+12, Randell Jesup wrote: >I added these stats originally, and they are now mostly superseded by the >stats provided by VideoPlaybackQuality. So I support their removal (in fact >I suggested to Tim that he remove them). > >Adding telemetry to learn how oft

Re: Intent to unship: moz*Frames attributes of HTMLVideoElement

On Fri, Jul 7, 2017 at 5:57 PM, Ehsan Akhgari wrote: > Yes indeed. (I just commented the same about unshipping another feature in > a different thread, so I won't repeat literally all of the same points here, > but they all apply here too!) I created https://wiki.mozilla.org/WebAPI/ExposureGuid

Re: Intent to unship: moz*Frames attributes of HTMLVideoElement

On Monday, July 10, 2017 at 3:28:07 PM UTC+12, Randell Jesup wrote: > >On Fri, Jul 7, 2017 at 11:54 AM, Jet Villegas 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

Re: Intent to unship: moz*Frames attributes of HTMLVideoElement

>On Fri, Jul 7, 2017 at 11:54 AM, Jet Villegas 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

Re: Intent to unship: moz*Frames attributes of HTMLVideoElement

On 07/07/2017 03:41 AM, Anne van Kesteren wrote: On Fri, Jul 7, 2017 at 8:51 AM, Jet Villegas wrote: Depending on what you find, we may have to keep this API around :-/ Yeah, I would expect us to follow the "normal" deprecation and remove path to be more confident in the eventual unshipping: Y

Re: Intent to unship: moz*Frames attributes of HTMLVideoElement

On 7/7/17 2:41 AM, Anne van Kesteren wrote: > On Fri, Jul 7, 2017 at 8:51 AM, Jet Villegas wrote: >> Depending on what you find, we may have to keep this API around :-/ > > Yeah, I would expect us to follow the "normal" deprecation and remove > path to be more confident in the eventual unshipping

Re: Intent to unship: moz*Frames attributes of HTMLVideoElement

On Fri, Jul 7, 2017 at 8:51 AM, Jet Villegas wrote: > Depending on what you find, we may have to keep this API around :-/ Yeah, I would expect us to follow the "normal" deprecation and remove path to be more confident in the eventual unshipping: 1. Gather telemetry on how often these APIs are us

Re: Intent to unship: moz*Frames attributes of HTMLVideoElement

Please take a closer look at some of these: https://github.com/search?utf8=%E2%9C%93&q=mozParsedFrames+extension%3Ajs&type=Code&ref=advsearch&l=&l= Depending on what you find, we may have to k

Re: Intent to unship: moz*Frames attributes of HTMLVideoElement

On Fri, Jul 7, 2017 at 11:54 AM, Jet Villegas 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.

Re: Intent to unship: moz*Frames attributes of HTMLVideoElement

What do we expect to break? Who's out there using these APIs now? Thanks, --Jet On Thu, Jul 6, 2017 at 8:21 PM, Tim Huang wrote: > I intent to unship the support of moz*Frames of HTMLVideoElement including > * HTMLVideoElement.mozParsedFrames > * HTMLVideoElement.mozDecodedFrames >

Intent to unship: moz*Frames attributes of HTMLVideoElement

I intent to unship the support of moz*Frames of HTMLVideoElement including * HTMLVideoElement.mozParsedFrames * HTMLVideoElement.mozDecodedFrames * HTMLVideoElement.mozPresentedFrames * HTMLVideoElement.mozPaintedFrames * HTMLVideoElement.mozFrameDelay in Bug 1379050 [1]. The r