[chromium] Make sure the touch-points in the touch-events have the correct state.
https://bugs.webkit.org/show_bug.cgi?id=98110 Patch by Sadrul Habib Chowdhury <firstname.lastname@example.org> on 2012-10-02 Reviewed by Adam Barth. Source/WebKit/chromium: It is necessary for the WebTouchPoints in the reconstructed WebTouchEvent to have the correct state. Without this change, the states were always unknown. * src/WebInputEventConversion.cpp: (WebKit::toWebTouchPointState): (WebKit): (WebKit::addTouchPoints): (WebKit::WebTouchEventBuilder::WebTouchEventBuilder): Tools: TestWebPlugin can now be configured to print out some details about events. For now, details for only touch events are printed. This is used to verify that touch-points in the touch-events are properly set. * DumpRenderTree/chromium/TestWebPlugin.cpp: (pointState): (printTouchList): (printEventDetails): (TestWebPlugin::TestWebPlugin): (TestWebPlugin::handleInputEvent): * DumpRenderTree/chromium/TestWebPlugin.h: (TestWebPlugin): LayoutTests: * platform/chromium/plugins/touch-events-details-expected.txt: Added. * platform/chromium/plugins/touch-events-details.html: Added. git-svn-id: http://svn.webkit.org/repository/webkit/trunk@130197 268f45cc-cd09-0410-ab3c-d52691b4dbfc