| OLD | NEW |
|---|
| (Empty) |
| 1 <h1 id="manifest_version">Manifest Version</h1>: | |
| 2 | |
| 3 <p> | |
| 4 One integer specifying the version of the manifest file format your package | |
| 5 requires. As of Chrome 18, developers <em>should</em> specify <code>2</code> | |
| 6 (without quotes) to use the format as described by this document: | |
| 7 </p> | |
| 8 | |
| 9 <pre class="prettyprint"><span class="str">"manifest_version"</span><span class=
"pun">:</span><span class="pln"> </span><span class="lit">2</span></pre> | |
| 10 | |
| 11 <p> | |
| 12 Consider manifest version 1 <em>deprecated</em> as of Chrome 18. Version 2 is | |
| 13 not yet <em>required</em>, but we will, at some point in the not-too-distant | |
| 14 future, stop supporting packages using deprecated manifest versions. Extensions, | |
| 15 applications, and themes that aren't ready to make the jump to the new manifest | |
| 16 version in Chrome 18 can either explicitly specify version <code>1</code>, or | |
| 17 leave the key off entirely. | |
| 18 </p> | |
| 19 | |
| 20 <p> | |
| 21 The changes between version 1 and version 2 of the manifest file format are | |
| 22 described in detail in <a href="http://developer.chrome.com/extensions/manifestV
ersion.html">the | |
| 23 <code>manifest_version</code> documentation.</a> | |
| 24 </p> | |
| 25 | |
| 26 <p class="caution"> | |
| 27 Setting <code>manifest_version</code> 2 in Chrome 17 or lower is not | |
| 28 recommended. If your extension needs to work in older versions of Chrome, | |
| 29 stick with version 1 for the moment. We'll give you ample warning before | |
| 30 version 1 stops working. | |
| 31 </p> | |
| OLD | NEW |
|---|
Chromium Code Reviews
Issue 14712010:
Revert 199633 "Doc server manifest page generation" (Closed)
Base URL: svn://svn.chromium.org/chrome/