Extensions Docs Server: Doc conversion script

chrome/common/extensions/docs/server2/templates/articles/app_known_issues.html

Index: chrome/common/extensions/docs/server2/templates/articles/app_known_issues.html
diff --git a/chrome/common/extensions/docs/server2/templates/articles/app_known_issues.html b/chrome/common/extensions/docs/server2/templates/articles/app_known_issues.html
new file mode 100644
index 0000000000000000000000000000000000000000..6e5148d46dd0869af2aa0528eb8dda0063645fc7
--- /dev/null
+++ b/chrome/common/extensions/docs/server2/templates/articles/app_known_issues.html
@@ -0,0 +1,57 @@
+<h1>Known Issues</h1>
+
+<p>Chrome's support for packaged apps is under active development and rapidly
+evolving, so there are still a few rough edges. Here's a list of known issues
+in the current <a href="https://tools.google.com/dlpage/chromesxs/">Chrome
+Canary</a>:</p>
+
+<p id="known-issues"></p>
+<p id="known-issues-error" style="position: absolute; top: -1000px; color: #333; padding: 1em; background: #eee;">
+  The list of known issues cannot be loaded at this time. You may be able to
+  see them on the <a href="http://code.google.com/p/chromium/issues/list?q=label:Hotlist-AppsKnownIssues">Chromium bug tracker</a>.
+</p>
+
+<script>
+  var xhr = new XMLHttpRequest();
+  xhr.onreadystatechange = function() {
+    if (xhr.readyState != 4) return;
+
+    if (xhr.status != 200) {
+      // We can't use display none/block, since in that case the error paragraph
+      // would be stripped by the template processor.
+      document.getElementById('known-issues-error').style.position = 'static';
+      return;
+    }
+    document.getElementById('known-issues').innerHTML = xhr.responseText;
+  };
+  xhr.open(
+      'GET', 'http://developer.chrome.com/app_known_issues_snippet.html', true);
+  xhr.send(null);
+</script>
+
+<p>
+If one of the above describes an issue you've run into, and you wish to be
+updated when it's resolved, click the star icon on the page header. Do not
+respond to the bug to say "me too" or ask "when will this be fixed?"; such
+updates can cause hundreds of emails to be sent. Add a comment only if you have
+information (such as a better test case or a suggested fix) that is likely
+to be helpful.
+</p>
+
+<h2>Can't find it in the list?</h2>
+
+<p>
+  If none of the issues listed above describe what you're running into, you
+  may wish to <a href="http://code.google.com/p/chromium/issues/list?can=2&q=Feature%3DApps+Type%3DBug">search</a>
+  the bug tracker, in case it has been reported but not marked as being known
+  yet.
+</p>
+
+<p>
+  If you still can't find something that matches the problem you're having, you
+  can <a href="https://code.google.com/p/chromium/issues/entry?template=Defect report from user&labels=Feature-Apps,Type-Bug,Area-Internals,Pri-2">report
+  the bug</a> on the Chromium bug tracker. Please include as many details as
+  possible in your bug report, including Chrome version number, operating
+  system, and any other relevant configuration details. Bug reports that attach
+  a small app that exhibits the problem are especially appreciated.
+</p>