Add initial support for handling touch events in desktop chrome AURA.

Add initial support for handling touch events in desktop chrome AURA. 

The change in render_widget_host_view_aura.cc is to prevent mouse events generated via touch events
on Windows being sent to the renderer. This is necessary as the touch events which are now sent to
the renderer ensure that clicks/moves, etc are handled correctly.

BUG=168427
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=175598

[sky, 2013-01-07 15:53:45]

https://codereview.chromium.org/11773007/diff/18001/ui/views/widget/native_wi...
File ui/views/widget/native_widget_win.cc (right):

https://codereview.chromium.org/11773007/diff/18001/ui/views/widget/native_wi...
ui/views/widget/native_widget_win.cc:785:
delegate_->OnTouchEvent(const_cast<ui::TouchEvent*>(&event));
Does this mean windows is now going to start generating touch events? And won't
views get both a touch and mouse event?

https://codereview.chromium.org/11773007/diff/18001/ui/views/win/hwnd_message...
File ui/views/win/hwnd_message_handler.cc (right):

https://codereview.chromium.org/11773007/diff/18001/ui/views/win/hwnd_message...
ui/views/win/hwnd_message_handler.cc:300: const int kDesktopChromeAuraTouchId =
9;
Do we need to make sure this doesn't conflict with anything?

[ananta, 2013-01-08 00:50:22]

https://codereview.chromium.org/11773007/diff/18001/ui/views/widget/native_wi...
File ui/views/widget/native_widget_win.cc (right):

https://codereview.chromium.org/11773007/diff/18001/ui/views/widget/native_wi...
ui/views/widget/native_widget_win.cc:785:
delegate_->OnTouchEvent(const_cast<ui::TouchEvent*>(&event));
On 2013/01/07 15:53:45, sky wrote:
> Does this mean windows is now going to start generating touch events? And
won't
> views get both a touch and mouse event?

As per our discussion, added checks in hwnd_message_handler to send touch events
only for AURA and to ignore Windows synthesized mouse messages.

https://codereview.chromium.org/11773007/diff/18001/ui/views/win/hwnd_message...
File ui/views/win/hwnd_message_handler.cc (right):

https://codereview.chromium.org/11773007/diff/18001/ui/views/win/hwnd_message...
ui/views/win/hwnd_message_handler.cc:300: const int kDesktopChromeAuraTouchId =
9;
On 2013/01/07 15:53:45, sky wrote:
> Do we need to make sure this doesn't conflict with anything?

We shouldn't be conflicting with anything. We have a limit of 12 touch event
sources with only one among them being active in a session. Exception being ASH
and desktop Chrome. Ash uses 10 as the touch id and desktop chrome with this
change will use 9.

[sky, 2013-01-08 04:52:13]

The TabStrip code likely needs to be updated as the result of this. Please file
a bug for tracking it.

https://codereview.chromium.org/11773007/diff/15006/ui/views/widget/native_wi...
File ui/views/widget/native_widget_win.cc (right):

https://codereview.chromium.org/11773007/diff/15006/ui/views/widget/native_wi...
ui/views/widget/native_widget_win.cc:785:
delegate_->OnTouchEvent(const_cast<ui::TouchEvent*>(&event));
Shouldn't this be a NOTREACHED?

[ananta, 2013-01-08 18:51:20]

Filed a bug https://code.google.com/p/chromium/issues/detail?id=168829 to track
the Tabstrip changes for touch events.

https://codereview.chromium.org/11773007/diff/15006/ui/views/widget/native_wi...
File ui/views/widget/native_widget_win.cc (right):

https://codereview.chromium.org/11773007/diff/15006/ui/views/widget/native_wi...
ui/views/widget/native_widget_win.cc:785:
delegate_->OnTouchEvent(const_cast<ui::TouchEvent*>(&event));
On 2013/01/08 04:52:13, sky wrote:
> Shouldn't this be a NOTREACHED?

Done.

[sky, 2013-01-08 19:13:38]

Can you try uploading again, your patch doesn't seem to have made it.

[ananta, 2013-01-08 19:14:54]

On 2013/01/08 19:13:38, sky wrote:
> Can you try uploading again, your patch doesn't seem to have made it.

Done. gcl upload had failed with the Base files missing error :(.

[sky, 2013-01-08 21:04:12]

LGTM