Issue 2115423002: Site Settings Android: Add UMA for measuring the Autoplay default setting value at profile startup.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Issue 2115423002: Site Settings Android: Add UMA for measuring the Autoplay default setting value at profile startup. (Closed)

Created:
4 years, 5 months ago by Finnur

Modified:
4 years, 5 months ago

Reviewers:

CC:
chromium-reviews

Base URL:
https://chromium.googlesource.com/chromium/src.git@2785

Target Ref:
refs/pending/branch-heads/2785

Project:
chromium

Visibility:
Public.

Site Settings Android: Add UMA for measuring the Autoplay default setting value at profile startup. BUG=622713 Review-Url: https://codereview.chromium.org/2115873002 Cr-Commit-Position: refs/heads/master@{#403473} (cherry picked from commit bd376092ad7bf6a2764f31eeee556f4b2c77584b) Committed: https://chromium.googlesource.com/chromium/src/+/59710b712a89a124805fe7725d57743569795aae

Created: 4 years, 5 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+10 lines, -0 lines)			Patch
	M	components/content_settings/core/browser/content_settings_default_provider.cc	View		1 chunk	+5 lines, -0 lines	0 comments	Download
	M	tools/metrics/histograms/histograms.xml	View		1 chunk	+5 lines, -0 lines	0 comments	Download

Total messages: 2 (1 generated)

Finnur

4 years, 5 months ago (2016-07-04 10:28:33 UTC) #2

Message was sent while issue was closed.

Committed patchset #1 (id:1) manually as
59710b712a89a124805fe7725d57743569795aae.