Comment #14 on issue 129638 by
gir...@chromium.org: Touch sends fake mouse
Win8 seems to work perfectly with this patch. Touching the screen does not
fire any touch events, unless you tap the screen (which generates a mouse
messages as per the spec.)
Win7 _mostly_ works. The OS generates a lot of mouse messages, and most of
them are ignored by chrome, except:
(1) when the user first touches an inactive window, a WM_MOUSEOVER and
WM_MOUSEMOVE are fired by the OS, without any flags. This is presumably
sent to activate the window. We have no means to identify that these are
touches.
(2) when a user starts touching an active window, a WM_MOUSEMOVE is sent
at the initial touch location without flags. Subsequent move messages get
flagged. Thus we get one "unflagged" mouse event for each touch.
We could possibly add some logic under Win7 to identify these simulated
mouse messages. We could test to see if the WM_MOUSEMOVE is near a
previous mouse move, we could watch for WM_MOUSEOVER messages that are not
at the edge of the window, we could wait for a second mousemove before we
send the message on.... In all of these cases, I expect that we'd be
introducing some fairly complex and flakey code, and so I recommend against
this kind of kludge.