New issue
Advanced search Search tips

Issue 668340 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Nov 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug



Sign in to add a comment

EME: Add metrics for usage from nested contexts

Project Member Reported by ddorwin@chromium.org, Nov 24 2016

Issue description

In order to require explicit enabling of EME in nested contexts (https://github.com/w3c/encrypted-media/issues/364), we would need to deprecate the current implicit enabling. In order to do that, we'd need metrics to tell us that pages aren't relying on it.

We should at least track when EME is used in an embedded context/iframe. It might be useful to separately track when uses where the origin is different from the top level context. If we think there will be a lot of uses that would actually show up, we could add RAPPOR, but I don't expect that to be the case, and that would require handling this in Chromium rather than Blink.
 
Labels: -M-57
Status: Fixed (was: Assigned)
UseCounter EncryptedMediaCrossOriginIframe was added back in July ( issue 689802 ). So marking this as fixed as I don't think a separate UMA is required.

The current values [1] indicate that as much as 0.0045% of page views use this. As this is counted next to EncryptedMediaSecureOrigin, using the data from Nov 14, it appears that ~5% (.003791/.075737) of EME usage uses a cross origin iframe.

There is a deprecation message indicating that the default will be changed in M64, which isn't that far away.

[1] https://www.chromestatus.com/metrics/feature/timeline/popularity/2036

Sign in to add a comment