Use method registration approach for creating events on core and modules.

Source/modules/InitModules.cpp

Index: Source/modules/InitModules.cpp
diff --git a/Source/modules/InitModules.cpp b/Source/modules/InitModules.cpp
index d0e8b903aece57d655baf0d9f44347c09df8a86f..0752e927df317b4396b084c86fdc8ac94cbac891 100644
--- a/Source/modules/InitModules.cpp
+++ b/Source/modules/InitModules.cpp
@@ -25,13 +25,10 @@ void ModulesInitializer::initEventTargetNames()
     EventTargetNames::initModules();
 }
 
-PassRefPtrWillBeRawPtr<Event> createEventModules(const String& eventType, ExceptionState& exceptionState)
+void ModulesInitializer::registerEventFactory()
 {
-    RefPtrWillBeRawPtr<Event> event = EventModulesFactory::create(eventType);
-    if (event)
-        return event.release();
-
-    return Document::createEvent(eventType, exceptionState);
+    CoreInitializer::registerEventFactory();
+    Document::registerEventFactory(new EventModulesFactory());

[eseidel, 2014/05/28 22:04:23]

create() functions are generally nicer than new, certainly in the case of
RefCounted.  I guess this is going away with oilpan though, so maybe that
doens't matter anymore.  This is OK.

[c.shu, 2014/05/29 15:06:49]

Ok. thanks.

 }
 
 } // namespace WebCore