Cleanup Tool WebUI: Add HTML content and styling with dummy JS

chrome/browser/ui/webui/cleanup_tool/cleanup_action_handler.cc

+// Copyright 2017 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 "chrome/browser/ui/webui/cleanup_tool/cleanup_action_handler.h"
+
+#include "base/bind.h"
+#include "base/values.h"
+#include "chrome/grit/generated_resources.h"
+#include "ui/base/l10n/l10n_util.h"
+
+CleanupActionHandler::CleanupActionHandler() {}
+
+void CleanupActionHandler::RegisterMessages() {
+  web_ui()->RegisterMessageCallback(
+      "requestLastScanResult",
+      base::Bind(&CleanupActionHandler::HandleRequestLastScanResult,
+                 base::Unretained(this)));
+}
+
+void CleanupActionHandler::HandleRequestLastScanResult(
+    const base::ListValue* args) {
+  // TODO(proberge): Return real information about the last run.
+  // TODO(proberge): Localize strings once they are finalized.
+  web_ui()->CallJavascriptFunctionUnsafe("cleanup.Manager.setDetectionStatus",

[tommycli, 2017/03/29 22:09:06]

For this call-and-response pattern, we use cr.sendWithPromise. See here for a
pattern of usage: https://cs.chromium.org/search/?q=areAllProfilesLocked&type=cs

That way, the caller does not have to be a singleton to receive a response...
and it enhances test-ability.

[tommycli, 2017/03/29 22:09:06]

So we aren't supposed to add any more CallJavascriptFunctionUnsafe calls.

All you have to do is call AllowJavascript() at the top of the method and use
CallJavascript instead.

[proberge, 2017/03/30 17:57:21]

Done.

[proberge, 2017/03/30 17:57:21]

Done.

+                                         base::Value(false), base::Value(false),
+                                         base::Value("No problems detected"),
+                                         base::Value("Last scanned today"));
+}