chrome/browser/resources/task_scheduler_internals/index.html - Issue 2349623003: Add a Browser Task Scheduler Chrome Internals Page

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: chrome/browser/resources/task_scheduler_internals/index.html

Issue 2349623003: Add a Browser Task Scheduler Chrome Internals Page (Closed)

Patch Set: Mac/Linux Fix + String Change Created 4 years, 3 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch

« no previous file with comments | « chrome/browser/resources/BUILD.gn ('k') | chrome/browser/resources/task_scheduler_internals_resources.grd » ('j') | chrome/browser/resources/task_scheduler_internals_resources.grd » ('J')
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

OLD	NEW
(Empty)
	1 <!DOCTYPE html>

	2 <html>
	xiyuan 2016/09/21 05:01:38 Do we need to worry about i18n ? If so, this shoul Do we need to worry about i18n ? If so, this should be <html i18n-values="dir:textdirection;lang:language"> and C++ data source calls webui::SetLoadTimeDataDefaults(...) to fill in the data. robliao 2016/09/21 22:32:03 This is an internal page for Chromium. Doesn't app Show quoted text On 2016/09/21 05:01:38, xiyuan wrote: > Do we need to worry about i18n ? If so, this should be > <html i18n-values="dir:textdirection;lang:language"> > > and C++ data source calls > webui::SetLoadTimeDataDefaults(...) > > to fill in the data. This is an internal page for Chromium. Doesn't appear to be necessary for the other internals page. We have no intention of i18n'ing this page.
	3 <!--

	4 Copyright 2016 The Chromium Authors. All rights reserved.

	5 Use of this source code is governed by a BSD-style license that can be

	6 found in the LICENSE file.

	7 -->

	8 <head>

	9 <title>Task Scheduler Internals</title>

	10 <link rel="stylesheet" href="chrome://resources/css/text_defaults.css">

	11 <script src="chrome://resources/js/load_time_data.js"></script>

	12 <script src="chrome://taskscheduler-internals/strings.js"></script>

	13 </head>

	14 <body>

	15 <h1>Task Scheduler Internals</h1>
	xiyuan 2016/09/21 05:01:38 Do we need to worry about i18n? If so, the text sh Do we need to worry about i18n? If so, the text should be in a grd file and populated via i18n-content attr (or friends). robliao 2016/09/21 22:32:03 See above. Show quoted text On 2016/09/21 05:01:38, xiyuan wrote: > Do we need to worry about i18n? If so, the text should be in a grd file and > populated via i18n-content attr (or friends). See above.
	16 Status: <span i18n-content="status"></span>

	17 <script src="chrome://resources/js/i18n_template.js"></script>

	18 </body>

	19 </html>

OLD	NEW