Issue 2861333002: Fixing white-screen problem for Curtain-mode Windows host connections

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 2861333002: Fixing white-screen problem for Curtain-mode Windows host connections (Closed)

Created:
3 years, 7 months ago by joedow

Modified:
3 years, 7 months ago

Reviewers:

CC:
chromium-reviews

Target Ref:
refs/branch-heads/3071

Project:
chromium

Visibility:
Public.

Fixing white-screen problem for Curtain-mode Windows host connections BUG=718143 Review-Url: https://codereview.chromium.org/2860203003 Cr-Commit-Position: refs/heads/master@{#469777} (cherry picked from commit 699aaa5fdd0d66259d48d32cbe586ab841076eb6) Review-Url: https://codereview.chromium.org/2861333002 . Cr-Commit-Position: refs/branch-heads/3071@{#435} Cr-Branched-From: a106f0abbf69dad349d4aaf4bcc4f5d376dd2377-refs/heads/master@{#464641} Committed: https://chromium.googlesource.com/chromium/src/+/4b28aa836f3063bfa8effa2027a376f938c8edc1

Created: 3 years, 7 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+5 lines, -3 lines)			Patch
	M	remoting/webapp/crd/js/desktop_connected_view.js	View		1 chunk	+3 lines, -1 line	0 comments	Download
	M	remoting/webapp/crd/js/desktop_viewport.js	View		2 chunks	+2 lines, -2 lines	0 comments	Download

Total messages: 2 (1 generated)

joedow

3 years, 7 months ago (2017-05-06 23:16:23 UTC) #2

Message was sent while issue was closed.

Committed patchset #1 (id:1) manually as
4b28aa836f3063bfa8effa2027a376f938c8edc1.