diff options
| author | sky@chromium.org <sky@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-05-04 17:50:18 +0000 |
|---|---|---|
| committer | sky@chromium.org <sky@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-05-04 17:50:18 +0000 |
| commit | 4c70b7a559f7188a2820b38e6dad2758a310b55c (patch) | |
| tree | b8f4fa39b556a7f0335b8b46fd5909af3b891ac6 /chrome/browser/search_engines/template_url_parser_unittest.cc | |
| parent | dd3423c1a6bf4e13da32694bb2e9ab2be43fd87d (diff) | |
| download | chromium_src-4c70b7a559f7188a2820b38e6dad2758a310b55c.zip chromium_src-4c70b7a559f7188a2820b38e6dad2758a310b55c.tar.gz chromium_src-4c70b7a559f7188a2820b38e6dad2758a310b55c.tar.bz2 | |
Lands the fix for bug 8088 from m0 (http://codereview.chromium.org/100022).
Here's his description:
Mouse hover out of context menu should un-select menu item.
All Context Menu's which are implemented with ChromeMenu is not properly
un-selecting the menu item when out of focus. The areas where this is affected
are: * Tabs * Bookmark bar * Bookmark managerThe others uses winapi for context
menus. Doesn't use ChromeMenu, uses HMENU, that explanes why the others work.
For this fix, I had to make sure that the MenuPart is always NONE when the mouse
is moved outside of the context menu regions, and that is always the case.
Hence, we can assure to remove selection. The same way it has been done for
SetSelection, I have used the same technique for this, but simpler.
BUG=8088
TEST=For the above mentioned affected areas, I brought up the context menu by
right clicking, and hovered over a menu item, then move the mouse horizontally
outside the context menu region, it deselected the item.
Review URL: http://codereview.chromium.org/102025
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@15220 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/search_engines/template_url_parser_unittest.cc')
0 files changed, 0 insertions, 0 deletions