Fix HWNDMessageHandler::OnSetCursor handling of HTERROR.

Handling HTERROR WM_SETCURSOR messages apparently causes a regression.
Modals don't pulse, beep, and come foreground when the parent is clicked.
This originally regressed with my http://crrev.com/188817.

BUG=375181
TEST=Clicking a browser with a window-modal dialog causes the dialog to pulse, beep, and the window pair to come foreground.
R=sky@chromium.org

Review URL: https://codereview.chromium.org/284313016

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@272353 0039d316-1c4b-4281-b951-d872f2087c98

ui/views/win/hwnd_message_handler.cc

@@ -1941,6 +1941,9 @@ LRESULT HWNDMessageHandler::OnSetCursor(UINT message,
     case HTCLIENT:
       SetCursor(current_cursor_);
       return 1;
+    case LOWORD(HTERROR):  // Use HTERROR's LOWORD value for valid comparison.
+      SetMsgHandled(FALSE);
+      break;
     default:
       // Use the default value, IDC_ARROW.
       break;