Issue 2678013003: Set kHasSeenWin10PromoPage in local_state instead of in profile prefs.

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 2678013003: Set kHasSeenWin10PromoPage in local_state instead of in profile prefs. (Closed)

Created:
3 years, 10 months ago by tmartino

Modified:
3 years, 10 months ago

Reviewers:

CC:
chromium-reviews

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

Project:
chromium

Visibility:
Public.

Set kHasSeenWin10PromoPage in local_state instead of in profile prefs. The pref is registered to the local state so the old code was incorrect. BUG=685799 Review-Url: https://codereview.chromium.org/2659643003 Cr-Commit-Position: refs/heads/master@{#446497} (cherry picked from commit 7c6a615b2b23452b33af668caab3945fe44b52a4) Review-Url: https://codereview.chromium.org/2678013003 . Cr-Commit-Position: refs/branch-heads/2987@{#342} Cr-Branched-From: ad51088c0e8776e8dcd963dbe752c4035ba6dab6-refs/heads/master@{#444943} Committed: https://chromium.googlesource.com/chromium/src/+/d76d75e529b4868ce056abde2ce07bbbd46b2c7e

Created: 3 years, 10 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+5 lines, -5 lines)			Patch
	M	chrome/browser/ui/webui/welcome_win10_ui.cc	View		3 chunks	+5 lines, -5 lines	0 comments	Download

Total messages: 2 (1 generated)

tmartino

3 years, 10 months ago (2017-02-06 19:53:32 UTC) #2

Message was sent while issue was closed.

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