Chrome side of having the WebKit FileSystem API use WebPermissionClient for checking if using fil...

content/worker/webworkerclient_proxy.cc

 // Copyright (c) 2011 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "content/worker/webworkerclient_proxy.h"
 
 #include "base/command_line.h"
 #include "base/message_loop.h"
 #include "content/common/content_switches.h"
 #include "content/common/file_system/file_system_dispatcher.h"
@@ skipping 131 matching lines @@
 }
 
 bool WebWorkerClientProxy::allowDatabase(WebFrame* frame,
                                          const WebString& name,
                                          const WebString& display_name,
                                          unsigned long estimated_size) {
   WebSecurityOrigin origin = frame->securityOrigin();
   if (origin.isEmpty())
     return false;
 
-  bool result;
-  if (!Send(new WorkerProcessHostMsg_AllowDatabase(route_id_,
-      GURL(origin.toString().utf8()), name, display_name, estimated_size,
-      &result)))
-    return false;
-
+  bool result = false;
+  Send(new WorkerProcessHostMsg_AllowDatabase(
+      route_id_, GURL(origin.toString().utf8()), name, display_name,
+      estimated_size, &result));
   return result;
 }
 
+bool WebWorkerClientProxy::allowFileSystem() {
+  bool result = false;
+  Send(new WorkerProcessHostMsg_AllowFileSystem(
+      route_id_, stub_->url().GetOrigin(), &result));
+  return result;
+}
+
 void WebWorkerClientProxy::openFileSystem(
     WebKit::WebFileSystem::Type type,
     long long size,
     bool create,
     WebKit::WebFileSystemCallbacks* callbacks) {
   ChildThread::current()->file_system_dispatcher()->OpenFileSystem(
       stub_->url().GetOrigin(), static_cast<fileapi::FileSystemType>(type),
       size, create, new WebFileSystemCallbackDispatcher(callbacks));
 }
 
@@ skipping 13 matching lines @@
 
   // This shuts down the process cleanly from the perspective of the browser
   // process, and avoids the crashed worker infobar from appearing to the new
   // page. It's ok to post several of theese, because the first executed task
   // will exit the message loop and subsequent ones won't be executed.
   MessageLoop::current()->PostDelayedTask(FROM_HERE,
       kill_process_factory_.NewRunnableMethod(
           &WebWorkerClientProxy::workerContextDestroyed),
           kMaxTimeForRunawayWorkerMs);
 }