Commit 151fe846 authored by kalman@chromium.org's avatar kalman@chromium.org

Devserver: remove the (apps) Known Issues. They're empty and not relevant anymore.

R=cduvall@chromium.org

Review URL: https://codereview.chromium.org/13604002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192927 0039d316-1c4b-4281-b951-d872f2087c98
parent 490e46f1
...@@ -552,14 +552,6 @@ button.google-button:active { ...@@ -552,14 +552,6 @@ button.google-button:active {
display: none; display: none;
} }
#known_issues {
background: #F5F5F5;
padding-top: 1px;
padding-bottom: 16px;
padding-right: 16px;
padding-left: 16px;
}
/* List with largeish images floated to the right. */ /* List with largeish images floated to the right. */
.imaged li { .imaged li {
clear: right; clear: right;
......
...@@ -7,8 +7,7 @@ See also the reference docs for the ...@@ -7,8 +7,7 @@ See also the reference docs for the
<a href="usb.html">USB API</a> <a href="usb.html">USB API</a>
and the and the
<a href="serial.html">Serial API</a>. <a href="serial.html">Serial API</a>.
The <a href="bluetooth.html">Bluetooth API</a> is also available The <a href="bluetooth.html">Bluetooth API</a> is also available;
(<a href="app_known_issues.html">known issues</a> still to be resolved);
we've include a link to a Bluetooth sample below. we've include a link to a Bluetooth sample below.
</p> </p>
......
<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>
{{+partials.known_issues}}
<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 id="cant_find_it">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>
...@@ -169,10 +169,6 @@ ...@@ -169,10 +169,6 @@
{ {
"title": "Samples", "title": "Samples",
"fileName": "samples.html" "fileName": "samples.html"
},
{
"title": "Known Issues",
"fileName": "app_known_issues.html"
} }
] ]
} }
......
<div id="known_issues">
<h3>Open known issues</h3>
{{?known_issues.open}}
<ul>
{{#known_issues.open}}
<li><a href="http://code.google.com/p/chromium/issues/detail?id={{id}}">
{{title}}
</a></li>
{{/known_issues.open}}
</ul>
{{:known_issues.open}}
<p>There are no open known issues at this time. You might be able to find more
on the <a href="http://code.google.com/p/chromium/issues/list?q=Hotlist%3DKnownIssue+Feature%3DApps">Chromium bug tracker</a>.</p>
{{/known_issues.open}}
<h3>Recently closed known issues</h3>
{{?known_issues.closed}}
<ul>
{{#known_issues.closed}}
<li><a href="http://code.google.com/p/chromium/issues/detail?id={{id}}">
{{title}}
</a></li>
{{/known_issues.closed}}
</ul>
{{:known_issues.closed}}
<p>There are no closed known issues at this time.</p>
{{/known_issues.closed}}
</div>
{{+partials.standard_apps_article article:intros.app_known_issues}}
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment