[InputEvent] Add InputEvent with basic interface behind a flag

third_party/WebKit/Source/core/dom/Node.cpp

Index: third_party/WebKit/Source/core/dom/Node.cpp
diff --git a/third_party/WebKit/Source/core/dom/Node.cpp b/third_party/WebKit/Source/core/dom/Node.cpp
index 897430f3629b36d3e6dd7e56c735839b6d37d5f1..31df6e6614094d8b50ba0f40a8acb4902e3c63a2 100644
--- a/third_party/WebKit/Source/core/dom/Node.cpp
+++ b/third_party/WebKit/Source/core/dom/Node.cpp
@@ -65,6 +65,7 @@
 #include "core/events/EventDispatcher.h"
 #include "core/events/EventListener.h"
 #include "core/events/GestureEvent.h"
+#include "core/events/InputEvent.h"
 #include "core/events/KeyboardEvent.h"
 #include "core/events/MouseEvent.h"
 #include "core/events/MutationEvent.h"
@@ -2077,7 +2078,9 @@ void Node::dispatchSimulatedClick(Event* underlyingEvent, SimulatedClickMouseEve
 
 void Node::dispatchInputEvent()
 {
-    dispatchScopedEvent(Event::createBubble(EventTypeNames::input));
+    InputEventInit eventInitDict;
+    eventInitDict.setBubbles(true);
+    dispatchScopedEvent(InputEvent::create(EventTypeNames::input, eventInitDict));

[chongz, 2016/02/09 15:35:59]

Do we prefer dictionary constructor or classic one?

[dtapuska, 2016/02/09 15:49:11]

this is fine I think; less code is often better. I think exposing another ctor
would be more code. We've done this approach with PointerEvents I think.

 }
 
 void Node::defaultEventHandler(Event* event)