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

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

Issue 14273041: Doc server manifest page generation (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: fix imports Created 7 years, 5 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
(Empty)
1 <h1 id="key">Manifest - Key</h1>
2
3 <p>
4 This value can be used to control
5 the unique ID of an extension, app, or theme when
6 it is loaded during development.
7 </p>
8
9 <p class="note">
10 <b>Note:</b> You don't usually need to
11 use this value. Instead, write your
12 code so that the key value doesn't matter
13 by using <a href="http://developer.chrome.com/extensions/overview.html#relative- urls">relative paths</a>
14 and <a href="http://developer.chrome.com/extensions/extension.html#method-getURL ">extension.getURL</a>.
15 </p>
16
17 <p>
18 To get a suitable key value, first
19 install your extension from a <code>.crx</code> file
20 (you may need to
21 <a href="https://chrome.google.com/webstore/developer/dashboard">upload your ext ension</a>
22 or <a href="http://developer.chrome.com/extensions/packaging.html">package it ma nually</a>).
23 Then, in your
24 <a href="http://www.chromium.org/user-experience/user-data-directory">user
25 data directory</a>, look in the file
26 <code>Default/Extensions/<em>&lt;extensionId&gt;</em>/<em>&lt;versionString&gt;< /em>/manifest.json</code>.
27 You will see the key value filled in there.
28 </p>
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698