Expose performance.memory in workers

public/web/WebSharedWorkerClient.h

Index: public/web/WebSharedWorkerClient.h
diff --git a/public/web/WebSharedWorkerClient.h b/public/web/WebSharedWorkerClient.h
index 89362f35c9d56f6f3e7cc0e184cf3dbe5e43cb53..f31c5da4e9f63320ebfd6ea69a6a09631ef734d8 100644
--- a/public/web/WebSharedWorkerClient.h
+++ b/public/web/WebSharedWorkerClient.h
@@ -53,6 +53,7 @@ public:
     virtual void workerScriptLoaded() = 0;
     virtual void workerScriptLoadFailed() = 0;
     virtual void selectAppCacheID(long long) = 0;
+    virtual bool enableMemoryInfo() { return false; }

[kinuko, 2014/02/28 05:23:29]

I'd like to avoid adding specific settings/preference method here.

I'm not very familiar with the settings code but, say, could we reuse
WebSettings interface or define new WebWorkerSettings to expose it to chromium?

[Pan, 2014/02/28 07:38:40]

I guess you mean we need a general method something like:
virtual WebSettings(WebWorkerSettings) workerSettings() { xxxx };

if that is true, either we need a new WebWorkerSettings in web platform API, or
we need change WebSettings, which is an pure abstract class currently. I think
the 1st solution is reasonable.
your idea?

thanks
Pan

[Pan, 2014/03/03 09:16:52]

Pachset 3 exposes WebWorkerSettings through WebAPI, can be set by chromium, see
another thread https://codereview.chromium.org/183153002/.

 
     // Returns the notification presenter for this worker context. Pointer
     // is owned by the object implementing WebSharedWorkerClient.