win: A potential fix for touch-event processing.

Dispatching a touch-event can end up destroying the window. Stop dispatching
queued up touch events if that is the case.

BUG=321533
R=sky@chromium.org

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@238127 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 238127
Work around for wrong coordinates in WM_GETTITLEBARINFOEX

Getting the wrong coordinates here means the tabstrip is unnecessarily
constrained to a smaller region. On most versions of Windows
WM_GETTITLEBARINFOEX returns screen coordinates for
WM_GETTITLEBARINFOEX. Since chrome is not dpi aware (currently) we
need to unscale these coordinates. Surface Pro seems to be unique, in
that it returns local coordinates (eg they don't need to be
scaled). There doesn't appear to be a clear way to detect this, so we
assume that if the minimize button is outside the bounds of the window
coordinates are scaled.

BUG=320133
TEST=verify tabstrip isn't constrained on surface pro and other
variants of windows, especially with scaling enabled.
R=ananta@chromium.org

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@238128 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 238128