Issue 2872693002: [MD settings] UMA and RevocationReporter in site settings

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 2872693002: [MD settings] UMA and RevocationReporter in site settings (Closed)

Created:
3 years, 7 months ago by dschuyler

Modified:
3 years, 7 months ago

Reviewers:

CC:
chromium-reviews

Target Ref:
refs/branch-heads/3071

Project:
chromium

Visibility:
Public.

[MD settings] UMA and RevocationReporter in site settings This CL adds UMA and Revocation reporting from site settings when a site exception is added or removed. The goal is to match the behavior of the old options. BUG=718544 Review-Url: https://codereview.chromium.org/2861793005 Cr-Commit-Position: refs/heads/master@{#469561} (cherry picked from commit b1c163ea6bf56b21576bed89fcf4162eebb2ab91) Review-Url: https://codereview.chromium.org/2872693002 . Cr-Commit-Position: refs/branch-heads/3071@{#452} Cr-Branched-From: a106f0abbf69dad349d4aaf4bcc4f5d376dd2377-refs/heads/master@{#464641} Committed: https://chromium.googlesource.com/chromium/src/+/f8e6f13bf85e4ec2783ddc843bd1d7ca09b51ab8

Created: 3 years, 7 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+44 lines, -20 lines)			Patch
	M	chrome/browser/ui/webui/settings/site_settings_handler.cc	View		4 chunks	+44 lines, -20 lines	0 comments	Download

Total messages: 2 (1 generated)

dschuyler

3 years, 7 months ago (2017-05-08 18:21:40 UTC) #2

Message was sent while issue was closed.

Committed patchset #1 (id:1) manually as
f8e6f13bf85e4ec2783ddc843bd1d7ca09b51ab8.