Support performance.now() in workers.

Source/modules/modules.gypi

Index: Source/modules/modules.gypi
diff --git a/Source/modules/modules.gypi b/Source/modules/modules.gypi
index 551dd63a2b4714bb4ba01284ceb065e5728f79e7..50b0ba746df1e33f37bb9936f818037132633856 100644
--- a/Source/modules/modules.gypi
+++ b/Source/modules/modules.gypi
@@ -91,6 +91,8 @@
       'notifications/NotificationCenter.idl',
       'notifications/NotificationPermissionCallback.idl',
       'notifications/WorkerContextNotifications.idl',
+      'performance/WorkerContextPerformance.idl',
+      'performance/WorkerPerformance.idl',
       'quota/DOMWindowQuota.idl',
       'quota/NavigatorStorageQuota.idl',
       'quota/StorageErrorCallback.idl',
@@ -398,6 +400,10 @@
       'notifications/NotificationPermissionCallback.h',
       'notifications/WorkerContextNotifications.cpp',
       'notifications/WorkerContextNotifications.h',
+      'performance/WorkerContextPerformance.cpp',
+      'performance/WorkerContextPerformance.h',
+      'performance/WorkerPerformance.cpp',
+      'performance/WorkerPerformance.h',

[abarth-chromium, 2013/06/12 23:13:46]

Will we be able to add the main-thread WebPerformance code to this module as
well?  My understanding is that at least some of it is tightly coupled with
FrameLoader and other core classes...

[James Simonsen, 2013/06/12 23:16:43]

Yes, that's the intent. The first thing I want to do is move all of the
page/Performance* files here.

Moving the stuff in loader/ will be harder as you say. I don't have a plan for
that right now.

       'quota/DOMWindowQuota.cpp',
       'quota/DOMWindowQuota.h',
       'quota/NavigatorStorageQuota.cpp',