-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove definitions/interface for corruptedFrames. #20
Conversation
Media WG resolved to remove this field at TPAC. https://www.w3.org/2019/09/19-mediawg-minutes.html#resolution01 Most UAs have not implemented corrupted frames and have no means to do so. Serious corruption will generally produce a decode error. This may may not be logically associated with particular frames. Less serious corruption may produce artifacts in the output, but in most cases it is not feasible for a UA to know that this has occurred.
@mounirlamouri, pls review. |
+1 |
Text LGTM. Only question, and this could be a follow-up, is given that it was implemented by many, should we have a note in the spec that previous versions used to have the attribute? Or does Mozilla and Apple expect to drop this? |
Mounir approved offline. |
…lity' r=bzbarsky According to [1], we're going to deprecate this attribute. [1] w3c/media-playback-quality#20 Differential Revision: https://phabricator.services.mozilla.com/D56621 --HG-- extra : moz-landing-system : lando
…lity' r=bzbarsky According to [1], we're going to deprecate this attribute. [1] w3c/media-playback-quality#20 Differential Revision: https://phabricator.services.mozilla.com/D56621 UltraBlame original commit: a2bf666e174210a67ea2a6b70957685b58aad0eb
…lity' r=bzbarsky According to [1], we're going to deprecate this attribute. [1] w3c/media-playback-quality#20 Differential Revision: https://phabricator.services.mozilla.com/D56621 UltraBlame original commit: a2bf666e174210a67ea2a6b70957685b58aad0eb
…lity' r=bzbarsky According to [1], we're going to deprecate this attribute. [1] w3c/media-playback-quality#20 Differential Revision: https://phabricator.services.mozilla.com/D56621 UltraBlame original commit: a2bf666e174210a67ea2a6b70957685b58aad0eb
…lity' r=bzbarsky According to [1], we're going to deprecate this attribute. [1] w3c/media-playback-quality#20 Differential Revision: https://phabricator.services.mozilla.com/D56621
Firefox 73 removed support for corruptedVideoFrames; Chrome never actually implemented support for it at all; and it has now been dropped completely from the spec. See https://bugzilla.mozilla.org/show_bug.cgi?id=1602163 and w3c/media-playback-quality#20 and w3c/media-playback-quality@f7cf7b1
Blink never implemented corruptedVideoFrames support, right? https://developer.mozilla.org/en-US/docs/Web/API/VideoPlaybackQuality/corruptedVideoFrames#Browser_compatibility and https://github.com/mdn/browser-compat-data/blob/master/api/VideoPlaybackQuality.json#L58-L64 claim that Chrome support was added in Chrome 23, but that appears to be wrong. So I’ve submitted mdn/browser-compat-data@79558e4 to get those updated. If any of that’s wrong, please comment there or here. |
Firefox 73 removed support for corruptedVideoFrames; Chrome never actually implemented support for it at all; and it has now been marked as deprecated in the spec. See https://bugzilla.mozilla.org/show_bug.cgi?id=1602163 and w3c/media-playback-quality#20 and w3c/media-playback-quality@f7cf7b1
Firefox 73 removed support for corruptedVideoFrames; Chrome never actually implemented support for it at all; and it has now been marked as deprecated in the spec. See https://bugzilla.mozilla.org/show_bug.cgi?id=1602163 and w3c/media-playback-quality#20 and w3c/media-playback-quality@f7cf7b1
* Update getVideoPlaybackQuality data for Chrome etc See https://bugs.chromium.org/p/chromium/issues/detail?id=644731#c47 and https://web-confluence.appspot.com/#!/catalog?q=%22getVideoPlaybackQuality%22 * Update Chrome Android getVideoPlaybackQuality data * Update corruptedVideoFrames support data & status Firefox 73 removed support for corruptedVideoFrames; Chrome never actually implemented support for it at all; and it has now been marked as deprecated in the spec. See https://bugzilla.mozilla.org/show_bug.cgi?id=1602163 and w3c/media-playback-quality#20 and w3c/media-playback-quality@f7cf7b1 * Update corruptedVideoFrames Chrome support data See https://github.com/mdn/browser-compat-data/pull/5452/files#r365296590 and https://storage.googleapis.com/chromium-find-releases-static/6c2.html#6c2d803 * Update corruptedVideoFrames Opera Android support See #5452 (comment)
Media WG resolved to remove this field at TPAC.
https://www.w3.org/2019/09/19-mediawg-minutes.html#resolution01
Most UAs have not implemented corrupted frames and have no means to do
so.
Serious corruption will generally produce a decode error. This may
may not be logically associated with particular frames. Less serious
corruption may produce artifacts in the output, but in most cases it is
not feasible for a UA to know that this has occurred.