New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 687169 link

Starred by 1 user

Issue metadata

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

Blocked on:
issue 652336



Sign in to add a comment

Consider adding UseCounters specific for extensions

Project Member Reported by rbyers@chromium.org, Jan 31 2017

Issue description

In  issue 652336  I updated the new UseCounters to not track usage from internal and extension pages.  In some rare cases (like the DeprecatedFlexboxChromeExtension UseCounter), extensions are specifically what we want to see.

Perhaps it IS worth adding a separate histogram to track usage specifically inside extension URLs?
 

Comment 1 by mkwst@chromium.org, Jan 31 2017

I think this is indeed worthwhile; without an understanding of how things _are_ used inside extensions, it's difficult to justify decisions about how things _should_ work. For instance, https://www.chromestatus.com/metrics/feature/timeline/popularity/662 tells me that I'm going to have a hard time enforcing mixed content checks inside extensions, and is something I'm keeping my eye on for the future. We're flying blind without that data.
Cc: mkwst@chromium.org
Labels: -Pri-3 M-60 Pri-2
Owner: lunalu@chromium.org
Luna, I think what we should do here is add at least one new histogram - Blink.UseCounter.Extensions.Features which we switch to using instead of Blink.UseCounter.Features in UseCounter::didCommitLoad if the URL is a chrome-extension:// URL (instead of disabling reporting completely).

Status: Started (was: Assigned)
Project Member

Comment 4 by bugdroid1@chromium.org, May 20 2017

Comment 5 by lunalu@chromium.org, May 23 2017

Status: Fixed (was: Started)

Comment 6 by rbyers@chromium.org, Jul 18 2017

Owner: loonyb...@chromium.org

Sign in to add a comment