Add SetImageData api to chrome.clipboard.

extensions/browser/api/clipboard/clipboard_api.cc

 // Copyright (c) 2016 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 "extensions/browser/api/clipboard/clipboard_api.h"
 
 #include <utility>
 
 #include "base/lazy_instance.h"
 #include "base/memory/ptr_util.h"
 #include "base/values.h"
 #include "extensions/browser/event_router.h"
+#include "extensions/browser/extensions_browser_client.h"
 #include "extensions/common/api/clipboard.h"
 #include "ui/base/clipboard/clipboard_monitor.h"
 
 namespace extensions {
 
 namespace clipboard = api::clipboard;
 
 static base::LazyInstance<BrowserContextKeyedAPIFactory<ClipboardAPI>>
     g_factory = LAZY_INSTANCE_INITIALIZER;
 
@@ skipping 17 matching lines @@
   if (router &&
       router->HasEventListener(clipboard::OnClipboardDataChanged::kEventName)) {
     std::unique_ptr<Event> event(
         new Event(events::CLIPBOARD_ON_CLIPBOARD_DATA_CHANGED,
                   clipboard::OnClipboardDataChanged::kEventName,
                   base::MakeUnique<base::ListValue>()));
     router->BroadcastEvent(std::move(event));
   }
 }
 
+ClipboardSetImageDataFunction::~ClipboardSetImageDataFunction() {}
+
+ExtensionFunction::ResponseAction ClipboardSetImageDataFunction::Run() {
+  std::unique_ptr<clipboard::SetImageData::Params> params(
+      clipboard::SetImageData::Params::Create(*args_));
+  EXTENSION_FUNCTION_VALIDATE(params.get());
+  SaveImageData(params->image_data, params->type);
+  return RespondLater();
+}
+
+void ClipboardSetImageDataFunction::SaveImageData(
+    const std::vector<char>& image_data,
+    const std::string& type) {
+  ExtensionsBrowserClient::Get()->SaveImageDataToClipboard(

[dcheng, 2016/10/04 05:13:27]

I might be missing something, but can the ExtensionFunction just use the helper
directly instead of going through ContentBrowserClient? From a layering
perspective, it would be nice not to have to expose extension-specific
functionality there.

[jennyz, 2016/10/04 23:53:54]

The image decoding code we used is under chrome/browser, which
extensions/browser/api code can not depends on, so we have to access it via
ExtensionsBrowserClient interface.

+      image_data, type,
+      base::Bind(&ClipboardSetImageDataFunction::OnSaveImageDataSuccess, this),
+      base::Bind(&ClipboardSetImageDataFunction::OnSaveImageDataError, this));
+}
+
+void ClipboardSetImageDataFunction::OnSaveImageDataSuccess() {
+  Respond(OneArgument(base::MakeUnique<base::FundamentalValue>(true)));
+}
+
+void ClipboardSetImageDataFunction::OnSaveImageDataError() {
+  Respond(OneArgument(base::MakeUnique<base::FundamentalValue>(false)));
+}
+
 }  // namespace extensions