Primary eng (and PM) emails
Link to “Intent to Deprecate” thread
https://groups.google.com/a/chromium.org/d/msg/blink-dev/DULRMEUkeJw/9HXn55X1gj4J
Summary
Motivation
The API has been deprecated for a release cycle to give developers a heads up. Usage is low.
Usage information from UseCounter
PrefixedVideoSupportsFullscreen: 0.009200893528
PrefixedVideoDisplayingFullscreen: 0.001510093115
PrefixedVideoEnterFullscreen: 0.0003490447336
PrefixedVideoExitFullscreen: 0.0003053643543
PrefixedVideoEnterFullScreen: 0.00002037975147
PrefixedVideoExitFullScreen: 0.00001725972437
Source: https://groups.google.com/a/chromium.org/d/msg/blink-dev/ze27T2M682w/SM3hGfQpKnoJ
Compatibility Risk
When removed, sites that use *only* this API with no fallback will simply stop supporting fullscreen. Given the usage counts this does not seem catastrophic, and it's likely that at least some of the current pages using this would fall back to another code path if the APIs were removed.
Row on feature dashboard?
http://www.chromestatus.com/metrics/feature/timeline/popularity/166
On Thu, Mar 6, 2014 at 1:21 AM, Anton Vayvod <ava...@chromium.org> wrote:The site is YouTube, for those who didn't follow the link. Has someone
> This removal rendered at least one very popular site unusable in Chrome for
> Android: https://code.google.com/p/chromium/issues/detail?id=347922 (I
> reverted the patch locally and confirm that it fixes the issue).
reached out to YouTube yet? It should be a simple fix.
> Could it be that the usage counters were wrong?They were implemented in the most ordinary manner, so I don't think
they're more wrong than any other counter. However, I don't know how
different products are weighted together, if something is hit on 100%
of sites on Android but 0% elsewhere, how would that show up in the
aggregate value?
Philip
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
On Wed, Mar 5, 2014 at 7:04 PM, Philip Jägenstedt <phi...@opera.com> wrote:
On Thu, Mar 6, 2014 at 1:21 AM, Anton Vayvod <ava...@chromium.org> wrote:The site is YouTube, for those who didn't follow the link. Has someone
> This removal rendered at least one very popular site unusable in Chrome for
> Android: https://code.google.com/p/chromium/issues/detail?id=347922 (I
> reverted the patch locally and confirm that it fixes the issue).
reached out to YouTube yet? It should be a simple fix.Since we can't trust the useCounter, it's unlikely that it is just YouTube that is affected.Maybe it's best to revert the change until we're sure that this doesn't a lot of broken video sites.
Adam
For my part, I'd like to understand the situation better before jumping to conclusions.
Adam
On Thu, 06 Mar 2014 04:04:56 +0100, Philip Jägenstedt <phi...@opera.com> wrote:
On Thu, Mar 6, 2014 at 1:21 AM, Anton Vayvod <ava...@chromium.org> wrote:
This removal rendered at least one very popular site unusable in Chrome for
Android: https://code.google.com/p/chromium/issues/detail?id=347922 (I
reverted the patch locally and confirm that it fixes the issue).
The site is YouTube, for those who didn't follow the link. Has someone
reached out to YouTube yet? It should be a simple fix.
I think this is the interesting question.
Could it be that the usage counters were wrong?
They were implemented in the most ordinary manner, so I don't think
they're more wrong than any other counter. However, I don't know how
different products are weighted together, if something is hit on 100%
of sites on Android but 0% elsewhere, how would that show up in the
aggregate value?
Does Chrome on Android report usage data or do we only get usage data from desktop computers?
/Daniel
PrefixedVideoSupportsFullscreen: 0.04274067971
PrefixedVideoDisplayingFullscreen: 0.20405662243
PrefixedVideoEnterFullscreen: 0.01697920768
PrefixedVideoExitFullscreen: 0.00434704942
PrefixedVideoEnterFullScreen: 0.01596530432
PrefixedVideoExitFullScreen: 0.05012209208
YouTube team should roll out the fix tonight PST time. Our QA haven't found any other sites being broken yet so maybe we can avoid reverting the change.
if( Element.prototype.matches === undefined ) {Element.prototype.matches = Element.prototype.webkitMatchesSelector;}document.body.matches('body');
try {context = new AudioContext();} catch( err ) {context = new webkitAudioContext();}