Issue 1772183002: Resets hover state when ToolbarActionView is dragged

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 1772183002: Resets hover state when ToolbarActionView is dragged (Closed)

Created:
4 years, 9 months ago by varkha

Modified:
4 years, 9 months ago

Reviewers:

CC:
chromium-reviews

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

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

Project:
chromium

Visibility:
Public.

Resets hover state when ToolbarActionView is dragged HOVERED state is now reset when drag is started. The fix is similar to https://codereview.chromium.org/1517003002 BUG=590941 Review URL: https://codereview.chromium.org/1748903003 Cr-Commit-Position: refs/heads/master@{#378810} (cherry picked from commit fb50932d80d11040f5637b17173c072a61d15f5a) Committed: https://chromium.googlesource.com/chromium/src/+/5e0ad74dad20fc4fa14689d3ab62ec70d8840187

Created: 4 years, 9 months ago

Download [raw] [tar.bz2]

	Unified diffs	Side-by-side diffs	Stats (+22 lines, -4 lines)			Patch
M	ui/views/controls/button/custom_button.cc	View	2 chunks	+7 lines, -2 lines	0 comments	Download
M	ui/views/controls/button/custom_button_unittest.cc	View	6 chunks	+14 lines, -2 lines	0 comments	Download
M	ui/views/widget/widget.h	View	1 chunk	+1 line, -0 lines	0 comments	Download

Total messages: 2 (1 generated)

varkha

4 years, 9 months ago (2016-03-08 01:36:23 UTC) #2

Message was sent while issue was closed.

Committed patchset #1 (id:1) manually as
5e0ad74dad20fc4fa14689d3ab62ec70d8840187.