Add WebPointerProperties type.

public/web/WebTouchPoint.h

 /*
  * Copyright (C) 2010 Google Inc. All rights reserved.
  *
  * Redistribution and use in source and binary forms, with or without
  * modification, are permitted provided that the following conditions are
  * met:
  *
  *     * Redistributions of source code must retain the above copyright
  * notice, this list of conditions and the following disclaimer.
  *     * Redistributions in binary form must reproduce the above
@@ skipping 15 matching lines @@
  * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
  * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
  * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
  */
 
 #ifndef WebTouchPoint_h
 #define WebTouchPoint_h
 
 #include "../platform/WebCommon.h"
 #include "../platform/WebFloatPoint.h"
+#include "WebMouseProperties.h"
+#include "WebPointerProperties.h"
 
 namespace blink {
 
-class WebTouchPoint {
+// TODO(e_hakkinen): Replace WebTouchEvent with WebPointerEvent and remove
+//                   WebTouchEvent and this.
+class WebTouchPoint : public WebMouseProperties, public WebPointerProperties {

[Rick Byers, 2015/07/06 17:22:38]

I was originally thinking we'd use aggregation (i.e. a "pointerProperties field)
instead of inheritance since the use of multiple inheritance is a little
unusual.

But I like the idea of using inheritance to minimize the changes necessary to
the code.  As long as we're careful it should be fine.

 public:
     WebTouchPoint()
-        : id(0)
+        : WebMouseProperties()
+        , WebPointerProperties()
         , state(StateUndefined)
-        , radiusX(0)
-        , radiusY(0)
         , rotationAngle(0)
-        , force(0)
     {
     }
 
     enum State {
         StateUndefined,
         StateReleased,
         StatePressed,
         StateMoved,
         StateStationary,
         StateCancelled,
     };
 
-    int id;
     State state;
     WebFloatPoint screenPosition;
     WebFloatPoint position;

[Rick Byers, 2015/07/06 17:22:39]

These co-ordinate properties could eventually be moved into WebPointerProperties
too.  Don't try to do that here - there is some complexity (eg. point vs.
separate x/y members, floats vs. ints) but I don't expect it would be that hard
to do in a later CL.  Maybe add a TODO saying they should move?

[USE eero AT chromium.org, 2015/07/07 10:00:56]

Done.

 
-    float radiusX;
-    float radiusY;

[Rick Byers, 2015/07/06 17:22:39]

You can't just replace radiusX/radiusY with width/height - they have different
semantics in the case of rotation.  For now why not just keep them called
radiusX/radiusY?

In fact, it might be simplest if the first CL doesn't change the name of ANY
fields, then we don't need to change chromium at all.  We can always do specific
renames later if we want to change semantics, but it's not clear to me when
we'll actually need that.

[USE eero AT chromium.org, 2015/07/07 10:00:56]

Done.

     float rotationAngle;
-    float force;
 };
 
 } // namespace blink
 
 #endif