summaryrefslogtreecommitdiffstats
path: root/chrome/common/extensions/docs/pageActions.html
diff options
context:
space:
mode:
Diffstat (limited to 'chrome/common/extensions/docs/pageActions.html')
-rwxr-xr-xchrome/common/extensions/docs/pageActions.html46
1 files changed, 46 insertions, 0 deletions
diff --git a/chrome/common/extensions/docs/pageActions.html b/chrome/common/extensions/docs/pageActions.html
new file mode 100755
index 0000000..faf8a37
--- /dev/null
+++ b/chrome/common/extensions/docs/pageActions.html
@@ -0,0 +1,46 @@
+<!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>