Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(551)

Side by Side Diff: chrome/common/extensions/docs/server2/templates/articles/app_known_issues.html

Issue 10832042: Extensions Docs Server: Doc conversion script (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src
Patch Set: everything but svn stuff Created 8 years, 4 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 | Annotate | Revision Log
OLDNEW
(Empty)
1 <h1>Known Issues</h1>
2
3 <p>Chrome's support for packaged apps is under active development and rapidly
4 evolving, so there are still a few rough edges. Here's a list of known issues
5 in the current <a href="https://tools.google.com/dlpage/chromesxs/">Chrome
6 Canary</a>:</p>
7
8 <p id="known-issues"></p>
9 <p id="known-issues-error" style="position: absolute; top: -1000px; color: #333; padding: 1em; background: #eee;">
10 The list of known issues cannot be loaded at this time. You may be able to
11 see them on the <a href="http://code.google.com/p/chromium/issues/list?q=label :Hotlist-AppsKnownIssues">Chromium bug tracker</a>.
12 </p>
13
14 <script>
15 var xhr = new XMLHttpRequest();
16 xhr.onreadystatechange = function() {
17 if (xhr.readyState != 4) return;
18
19 if (xhr.status != 200) {
20 // We can't use display none/block, since in that case the error paragraph
21 // would be stripped by the template processor.
22 document.getElementById('known-issues-error').style.position = 'static';
23 return;
24 }
25 document.getElementById('known-issues').innerHTML = xhr.responseText;
26 };
27 xhr.open(
28 'GET', 'http://developer.chrome.com/app_known_issues_snippet.html', true);
29 xhr.send(null);
30 </script>
31
32 <p>
33 If one of the above describes an issue you've run into, and you wish to be
34 updated when it's resolved, click the star icon on the page header. Do not
35 respond to the bug to say "me too" or ask "when will this be fixed?"; such
36 updates can cause hundreds of emails to be sent. Add a comment only if you have
37 information (such as a better test case or a suggested fix) that is likely
38 to be helpful.
39 </p>
40
41 <h2>Can't find it in the list?</h2>
42
43 <p>
44 If none of the issues listed above describe what you're running into, you
45 may wish to <a href="http://code.google.com/p/chromium/issues/list?can=2&q=Fea ture%3DApps+Type%3DBug">search</a>
46 the bug tracker, in case it has been reported but not marked as being known
47 yet.
48 </p>
49
50 <p>
51 If you still can't find something that matches the problem you're having, you
52 can <a href="https://code.google.com/p/chromium/issues/entry?template=Defect r eport from user&labels=Feature-Apps,Type-Bug,Area-Internals,Pri-2">report
53 the bug</a> on the Chromium bug tracker. Please include as many details as
54 possible in your bug report, including Chrome version number, operating
55 system, and any other relevant configuration details. Bug reports that attach
56 a small app that exhibits the problem are especially appreciated.
57 </p>
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698