Issue 2151363002: Fixing a cursor position initialization problem

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 2151363002: Fixing a cursor position initialization problem (Closed)

Created:
4 years, 5 months ago by joedow

Modified:
4 years, 5 months ago

Reviewers:

CC:
chromium-reviews

Base URL:
https://chromium.googlesource.com/chromium/src.git@2785

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

Project:
chromium

Visibility:
Public.

Fixing a cursor position initialization problem This issue was caused during a recent refactoring. This CL adds the initialization code for Trackpad mode back. BUG=628034 Review-Url: https://codereview.chromium.org/2146303002 Cr-Commit-Position: refs/heads/master@{#405610} (cherry picked from commit 1bbf9d224609df203040da6e2d3d9f7d39c2cd91) Committed: https://chromium.googlesource.com/chromium/src/+/849830d4a9198614895cef5e31e1960f88271107

Created: 4 years, 5 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+31 lines, -7 lines)			Patch
	M	remoting/android/java/src/org/chromium/chromoting/DesktopCanvas.java	View		1 chunk	+12 lines, -0 lines	0 comments	Download
	M	remoting/android/java/src/org/chromium/chromoting/TouchInputHandler.java	View		4 chunks	+19 lines, -7 lines	0 comments	Download

Total messages: 2 (1 generated)

joedow

4 years, 5 months ago (2016-07-15 20:20:57 UTC) #2

Message was sent while issue was closed.

Committed patchset #1 (id:1) manually as
849830d4a9198614895cef5e31e1960f88271107.