Issue 2710763004: Show reauth dialog instead of signin dialog when trying to open a locked profile.

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 2710763004: Show reauth dialog instead of signin dialog when trying to open a locked profile. (Closed)

Created:
3 years, 10 months ago by Bernhard Bauer

Modified:
3 years, 10 months ago

Reviewers:
Bernhard Bauer

CC:
chromium-reviews

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

Project:
chromium

Visibility:
Public.

Show reauth dialog instead of signin dialog when trying to open a locked profile. BUG=687894 R=bauerb@chromium.org Review-Url: https://codereview.chromium.org/2692863004 Cr-Commit-Position: refs/heads/master@{#450386} (cherry picked from commit 58084dd8f1d79ce115ee976daa4f1d6b8d51481b) Review-Url: https://codereview.chromium.org/2710763004 . Cr-Commit-Position: refs/branch-heads/2987@{#640} Cr-Branched-From: ad51088c0e8776e8dcd963dbe752c4035ba6dab6-refs/heads/master@{#444943} Committed: https://chromium.googlesource.com/chromium/src/+/0dd0d42a2ea5eb0d180e76c2b75f6fae97809d98

Created: 3 years, 10 months ago

Download [raw] [tar.bz2]

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

Total messages: 2 (1 generated)

Bernhard Bauer

3 years, 10 months ago (2017-02-22 11:58:25 UTC) #2

Message was sent while issue was closed.

Committed patchset #1 (id:1) manually as
0dd0d42a2ea5eb0d180e76c2b75f6fae97809d98.