Issue 2860653004: [Merge to M59] Whitelisted clipboardRead Permission

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 2860653004: [Merge to M59] Whitelisted clipboardRead Permission (Closed)

Created:
3 years, 7 months ago by Ivan Šandrk

Modified:
3 years, 7 months ago

Reviewers:

CC:
chromium-reviews

Target Ref:
refs/branch-heads/3071

Project:
chromium

Visibility:
Public.

[Merge to M59] Whitelisted clipboardRead Permission Follow up to crrev.com/2794803003 - forgot to actually whitelist the permission. BUG=707864 Review-Url: https://codereview.chromium.org/2838173002 Cr-Commit-Position: refs/heads/master@{#466994} (cherry picked from commit 9074b2db8c610057e8ef1a2b3d53b93e7d23f918) Review-Url: https://codereview.chromium.org/2860653004 . Cr-Commit-Position: refs/branch-heads/3071@{#374} Cr-Branched-From: a106f0abbf69dad349d4aaf4bcc4f5d376dd2377-refs/heads/master@{#464641} Committed: https://chromium.googlesource.com/chromium/src/+/ebd27c6f674b70fd93d7681f0e16f4d29a097989

Created: 3 years, 7 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+3 lines, -4 lines)			Patch
	M	chrome/browser/chromeos/extensions/device_local_account_management_policy_provider.cc	View		1 chunk	+3 lines, -4 lines	0 comments	Download

Total messages: 2 (1 generated)

Ivan Šandrk

3 years, 7 months ago (2017-05-03 15:26:54 UTC) #2

Message was sent while issue was closed.

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