Update rich touch information to conform to standard

chrome/browser/renderer_host/render_widget_host_view_views.cc

Index: chrome/browser/renderer_host/render_widget_host_view_views.cc
diff --git a/chrome/browser/renderer_host/render_widget_host_view_views.cc b/chrome/browser/renderer_host/render_widget_host_view_views.cc
index b9ebf768e239fcf1454f88401e7ac4b2cc58a862..4810e1d1f7062a61cfcf6d651993f9d69982aa45 100644
--- a/chrome/browser/renderer_host/render_widget_host_view_views.cc
+++ b/chrome/browser/renderer_host/render_widget_host_view_views.cc
@@ -107,6 +107,13 @@ WebKit::WebInputEvent::Type TouchEventTypeFromEvent(
   }
 }
 
+void UpdateTouchParams(const views::TouchEvent* event,
+                       WebKit::WebTouchPoint* tpoint) {
+  tpoint->radiusX = event->radiusX();
+  tpoint->radiusY = event->radiusY();
+  tpoint->rotationAngle = event->angle();
+}
+
 void UpdateTouchPointPosition(const views::TouchEvent* event,
                               const gfx::Point& origin,
                               WebKit::WebTouchPoint* tpoint) {
@@ -563,6 +570,8 @@ views::View::TouchStatus RenderWidgetHostViewViews::OnTouchEvent(
   if (status != TOUCH_STATUS_START)
     status = TOUCH_STATUS_CONTINUE;
 
+  UpdateTouchParams(&event, point);

[rjkroege, 2011/06/08 17:17:33]

why did you make this a separate function?  Seems like the code could just be
inline?

[Yufeng Shen (Slow to review), 2011/06/08 17:30:13]

I thought in the future there might be more params get added so put them in a
function we get better readability and know where to update all those params. 

+
   // Update the location and state of the point.
   point->state = TouchPointStateFromEvent(&event);
   if (point->state == WebKit::WebTouchPoint::StateMoved) {