1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
|
!DOCTYPE html>
<!-- This page is a placeholder for generated extensions api doc. Note:
1) The <head> information in this page is significant, should be uniform
across api docs and should be edited only with knowledge of the
templating mechanism.
2) The <body> tag *must* retain id="body"
3) All <body>.innerHTML is genereated as an rendering step. If viewed in a
browser, it will be re-generated from the template, json schema and
authored overview content.
4) The <body>.innerHTML is also generated by an offline step so that this
page may easily be indexed by search engines.
TODO(rafaelw): Abstract this into a "pageshell" that becomes the single
version of page template shell and the "instance" pages (bookmarks.html,
etc...) can be generated with a build step.
-->
<!-- <html> must retain id="template -->
<html xmlns="http://www.w3.org/1999/xhtml">
<!-- <head> data is significant and loads the needed libraries and styles -->
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<title jscontent="pageTitle">pageTitle</title>
<link href="css/ApiRefStyles.css" rel="stylesheet" type="text/css">
<script type="text/javascript"
src="../../../third_party/jstemplate/jstemplate_compiled.js">
</script>
<script type="text/javascript" src="js/api_page_generator.js"></script>
<script>
// Re-render the page if the user-agent is chrome and it is being served as
// a file:/// scheme. This allows both the initial render to static as well
// as dynamic re-rendering for developers/doc-writers working on local changes.
window.onload = function() {
var chrome = navigator.userAgent.indexOf("Chrome") > -1;
var fileScheme = location.protocol == "file:";
var regenerate = chrome && fileScheme;
//if (regenerate) {
window.renderPage();
//}
}
</script>
</head>
<!-- <body> content is completely generated. Do not edit, as it will be
and rewritten. -->
<body class="hidden">
</body>
</html>
>>>>>>> .merge-right.r22299
=======
<!DOCTYPE html>
<!-- This page is a placeholder for generated extensions api doc. Note:
1) The <head> information in this page is significant, should be uniform
across api docs and should be edited only with knowledge of the
templating mechanism.
2) The <body> tag *must* retain id="body"
3) All <body>.innerHTML is genereated as an rendering step. If viewed in a
browser, it will be re-generated from the template, json schema and
authored overview content.
4) The <body>.innerHTML is also generated by an offline step so that this
page may easily be indexed by search engines.
TODO(rafaelw): Abstract this into a "pageshell" that becomes the single
version of page template shell and the "instance" pages (bookmarks.html,
etc...) can be generated with a build step.
-->
<!-- <html> must retain id="template -->
<html xmlns="http://www.w3.org/1999/xhtml">
<!-- <head> data is significant and loads the needed libraries and styles -->
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<title jscontent="pageTitle">pageTitle</title>
<link href="css/ApiRefStyles.css" rel="stylesheet" type="text/css">
<script type="text/javascript"
src="../../../third_party/jstemplate/jstemplate_compiled.js">
</script>
<script type="text/javascript" src="js/api_page_generator.js"></script>
<script>
// Re-render the page if the user-agent is chrome and it is being served as
// a file:/// scheme. This allows both the initial render to static as well
// as dynamic re-rendering for developers/doc-writers working on local changes.
window.onload = function() {
var chrome = navigator.userAgent.indexOf("Chrome") > -1;
var fileScheme = location.protocol == "file:";
var regenerate = chrome && fileScheme;
//if (regenerate) {
window.renderPage();
//}
}
</script>
</head>
<!-- <body> content is completely generated. Do not edit, as it will be
and rewritten. -->
<body class="hidden">
</body>
</html>
>>>>>>> .merge-right.r22299
=======
<!DOCTYPE html>
<!-- This page is a placeholder for generated extensions api doc. Note:
1) The <head> information in this page is significant, should be uniform
across api docs and should be edited only with knowledge of the
templating mechanism.
2) The <body> tag *must* retain id="body"
3) All <body>.innerHTML is genereated as an rendering step. If viewed in a
browser, it will be re-generated from the template, json schema and
authored overview content.
4) The <body>.innerHTML is also generated by an offline step so that this
page may easily be indexed by search engines.
TODO(rafaelw): Abstract this into a "pageshell" that becomes the single
version of page template shell and the "instance" pages (bookmarks.html,
etc...) can be generated with a build step.
-->
<!-- <html> must retain id="template -->
<html xmlns="http://www.w3.org/1999/xhtml">
<!-- <head> data is significant and loads the needed libraries and styles -->
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<title jscontent="pageTitle">pageTitle</title>
<link href="css/ApiRefStyles.css" rel="stylesheet" type="text/css">
<script type="text/javascript"
src="../../../third_party/jstemplate/jstemplate_compiled.js">
</script>
<script type="text/javascript" src="js/api_page_generator.js"></script>
<script>
// Re-render the page if the user-agent is chrome and it is being served as
// a file:/// scheme. This allows both the initial render to static as well
// as dynamic re-rendering for developers/doc-writers working on local changes.
window.onload = function() {
var chrome = navigator.userAgent.indexOf("Chrome") > -1;
var fileScheme = location.protocol == "file:";
var regenerate = chrome && fileScheme;
//if (regenerate) {
window.renderPage();
//}
}
</script>
</head>
<!-- <body> content is completely generated. Do not edit, as it will be
and rewritten. -->
<body class="hidden">
</body>
</html>
|
