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

Side by Side Diff: chrome/common/extensions/docs/templates/articles/manifest/manifest_version.html

Issue 219213007: Remove .html extension from links (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Created 6 years, 7 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
OLDNEW
1 <h1 id="manifest_version">Manifest Version</h1> 1 <h1 id="manifest_version">Manifest Version</h1>
2 2
3 <p> 3 <p>
4 One integer specifying the version of the manifest file format your package 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> 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: 6 (without quotes) to use the format as described by this document:
7 </p> 7 </p>
8 8
9 <pre data-filename="manifest.json"> 9 <pre data-filename="manifest.json">
10 "manifest_version": 2 10 "manifest_version": 2
11 </pre> 11 </pre>
12 12
13 <p> 13 <p>
14 Consider manifest version 1 <em>deprecated</em> as of Chrome 18. Version 2 is 14 Consider manifest version 1 <em>deprecated</em> as of Chrome 18. Version 2 is
15 not yet <em>required</em>, but we will, at some point in the not-too-distant 15 not yet <em>required</em>, but we will, at some point in the not-too-distant
16 future, stop supporting packages using deprecated manifest versions. Extensions, 16 future, stop supporting packages using deprecated manifest versions. Extensions,
17 applications, and themes that aren't ready to make the jump to the new manifest 17 applications, and themes that aren't ready to make the jump to the new manifest
18 version in Chrome 18 can either explicitly specify version <code>1</code>, or 18 version in Chrome 18 can either explicitly specify version <code>1</code>, or
19 leave the key off entirely. 19 leave the key off entirely.
20 </p> 20 </p>
21 21
22 <p> 22 <p>
23 The changes between version 1 and version 2 of the manifest file format are 23 The changes between version 1 and version 2 of the manifest file format are
24 described in detail in <a href="http://developer.chrome.com/extensions/manifestV ersion.html">the 24 described in detail in <a href="http://developer.chrome.com/extensions/manifestV ersion">the
25 <code>manifest_version</code> documentation.</a> 25 <code>manifest_version</code> documentation.</a>
26 </p> 26 </p>
27 27
28 <p class="caution"> 28 <p class="caution">
29 Setting <code>manifest_version</code> 2 in Chrome 17 or lower is not 29 Setting <code>manifest_version</code> 2 in Chrome 17 or lower is not
30 recommended. If your extension needs to work in older versions of Chrome, 30 recommended. If your extension needs to work in older versions of Chrome,
31 stick with version 1 for the moment. We'll give you ample warning before 31 stick with version 1 for the moment. We'll give you ample warning before
32 version 1 stops working. 32 version 1 stops working.
33 </p> 33 </p>
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698