Index: chrome/browser/resources/task_scheduler_internals/index.html |
diff --git a/chrome/browser/resources/task_scheduler_internals/index.html b/chrome/browser/resources/task_scheduler_internals/index.html |
new file mode 100644 |
index 0000000000000000000000000000000000000000..ab40dd89454dd9d394adbe89bb2610d44a719d54 |
--- /dev/null |
+++ b/chrome/browser/resources/task_scheduler_internals/index.html |
@@ -0,0 +1,19 @@ |
+<!DOCTYPE html> |
+<html> |
xiyuan
2016/09/21 05:01:38
Do we need to worry about i18n ? If so, this shoul
robliao
2016/09/21 22:32:03
This is an internal page for Chromium. Doesn't app
|
+<!-- |
+Copyright 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. |
+--> |
+ <head> |
+ <title>Task Scheduler Internals</title> |
+ <link rel="stylesheet" href="chrome://resources/css/text_defaults.css"> |
+ <script src="chrome://resources/js/load_time_data.js"></script> |
+ <script src="chrome://taskscheduler-internals/strings.js"></script> |
+ </head> |
+ <body> |
+ <h1>Task Scheduler Internals</h1> |
xiyuan
2016/09/21 05:01:38
Do we need to worry about i18n? If so, the text sh
robliao
2016/09/21 22:32:03
See above.
|
+ Status: <span i18n-content="status"></span> |
+ <script src="chrome://resources/js/i18n_template.js"></script> |
+ </body> |
+</html> |