Issue 2690563003: Fix names of MobileFre.Progress histograms.

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 2690563003: Fix names of MobileFre.Progress histograms. (Closed)

Created:
3 years, 10 months ago by Alexei Svitkine (slow)

Modified:
3 years, 10 months ago

Reviewers:
Ted C

CC:
chromium-reviews

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

Project:
chromium

Visibility:
Public.

Fix names of MobileFre.Progress histograms. I accidentally broke this in a refactoring here: https://codereview.chromium.org/2466723002/ BUG=690655 TBR=tedchoc@chromium.org Review-Url: https://codereview.chromium.org/2689613002 Cr-Commit-Position: refs/heads/master@{#449450} (cherry picked from commit 1e3d6c77d25e3cd97e776fa3b5427f883341c854) Review-Url: https://codereview.chromium.org/2690563003 . Cr-Commit-Position: refs/branch-heads/2987@{#436} Cr-Branched-From: ad51088c0e8776e8dcd963dbe752c4035ba6dab6-refs/heads/master@{#444943} Committed: https://chromium.googlesource.com/chromium/src/+/eb950b91fbff62f4b05095807bb6c0eba9ac4b10

Created: 3 years, 10 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+2 lines, -2 lines)			Patch
	M	chrome/android/java/src/org/chromium/chrome/browser/firstrun/FirstRunActivity.java	View		1 chunk	+2 lines, -2 lines	0 comments	Download

Total messages: 2 (1 generated)

Alexei Svitkine (slow)

3 years, 10 months ago (2017-02-10 15:32:17 UTC) #2

Message was sent while issue was closed.

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