Impelement InputDevice.firesTouchEvents

Source/core/events/InputDevice.idl

Index: Source/core/events/InputDevice.idl
diff --git a/Source/core/events/InputDevice.idl b/Source/core/events/InputDevice.idl
new file mode 100644
index 0000000000000000000000000000000000000000..64254db1d32c39337ccef039fd1c19bf99471327
--- /dev/null
+++ b/Source/core/events/InputDevice.idl
@@ -0,0 +1,22 @@
+// Copyright 2015 The Chromium Authors. All rights reserved.

[Rick Byers, 2015/05/28 00:21:57]

as discussed offline, maybe this is a good time to create Source/core/input? 
EventHandler.* could go there (but that can be a separate CL).  Technically
InputDevice isn't strictly coupled to events (we hope to some day have some
InputDevice.getAllDevices API).

[tdresser, 2015/05/28 15:03:21]

+1

[lanwei, 2015/05/28 18:14:42]

I will create a new fold in another CL, and move InputDevice and EventHandler to
it.

+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+// Represents an input device (or group of related devices -- now we do not
+// distinguish each different input device. We only have two devices right now,
+// one represents all the devices which send touch events, the other one covers
+// all other devices which do not send touch events, because now all we care
+// about is if the input device fires touch events or not).
+// To ease implementation, developers cannot rely on comparing two InputDevice

[tdresser, 2015/05/28 15:03:21]

I'd move the "To ease implementation..." section above the description of how we
only have two InputDevices, and then get rid of the "Eg. two mice with the
same..."

Something like:

Represents an input device (or group of related devices).
To ease implementation, developers cannot rely on comparing 
two InputDevice instances for equality. We only have two InputDevice instances
right now:
one represents all the devices which send touch events, the other one covers
all other devices which do not send touch events, because currently all we care
about is if the input device fires touch events or not.

[lanwei, 2015/05/28 18:14:43]

Done.

+// instances for equality.  Eg. two mice with the same properties in a system may
+// appear as a single InputDevice instance.
+[
+    Constructor(optional InputDeviceInit deviceInitDict),
+    RuntimeEnabled=InputDevice,
+] interface InputDevice {
+    
+    // Whether this device dispatches touch events for movement.  This is used to detect
+    // mouse events which represent only an action that has already been handled  by
+    // touch event handlers.
+    readonly attribute boolean firesTouchEvents;
+};