When pressing Windows mouse (Logitech, MS, etc..) buttons bound to browser forward/back actions and generating WM_XBUTTONxxx messages, the widget mouse handler would mark the events as handled. This would keep the DefWindowProc from being called and thus squelch the generation of proper a WM_APPCOMMAND message.

This would make those buttons ineffective when the mouse cursor was over any widget/view. The browser content view, however, wouldn't squelch those messages and the WM_APPCOMMAND message is properly generated.

BUG=329895
TEST=Using a mouse equipped with back/forward buttons, test by ensuring the mouse cursor is over the omnibox, bookmarkbar, tabs, or infobar before pressing the back/forward buttons.

Review-Url: https://codereview.chromium.org/2372413002
Cr-Commit-Position: refs/heads/master@{#421646}
1 file changed