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

Side by Side Diff: chrome/common/extensions/docs/autoupdate.html

Issue 7778017: Update references to the extension gallery. (Closed) Base URL: svn://chrome-svn/chrome/trunk/src/
Patch Set: '' Created 9 years, 3 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
1 <!DOCTYPE html><!-- This page is a placeholder for generated extensions api doc. Note: 1 <!DOCTYPE html><!-- This page is a placeholder for generated extensions api doc. Note:
2 1) The <head> information in this page is significant, should be uniform 2 1) The <head> information in this page is significant, should be uniform
3 across api docs and should be edited only with knowledge of the 3 across api docs and should be edited only with knowledge of the
4 templating mechanism. 4 templating mechanism.
5 3) All <body>.innerHTML is genereated as an rendering step. If viewed in a 5 3) All <body>.innerHTML is genereated as an rendering step. If viewed in a
6 browser, it will be re-generated from the template, json schema and 6 browser, it will be re-generated from the template, json schema and
7 authored overview content. 7 authored overview content.
8 4) The <body>.innerHTML is also generated by an offline step so that this 8 4) The <body>.innerHTML is also generated by an offline step so that this
9 page may easily be indexed by search engines. 9 page may easily be indexed by search engines.
10 --><html xmlns="http://www.w3.org/1999/xhtml"><head> 10 --><html xmlns="http://www.w3.org/1999/xhtml"><head>
(...skipping 334 matching lines...) Expand 10 before | Expand all | Expand 10 after
345 <p id="classSummary" style="display: none; "> 345 <p id="classSummary" style="display: none; ">
346 For information on how to use experimental APIs, see the <a href="expe rimental.html">chrome.experimental.* APIs</a> page. 346 For information on how to use experimental APIs, see the <a href="expe rimental.html">chrome.experimental.* APIs</a> page.
347 </p> 347 </p>
348 348
349 <!-- STATIC CONTENT PLACEHOLDER --> 349 <!-- STATIC CONTENT PLACEHOLDER -->
350 <div id="static"><div id="pageData-name" class="pageData">Autoupdating</ div> 350 <div id="static"><div id="pageData-name" class="pageData">Autoupdating</ div>
351 <div id="pageData-showTOC" class="pageData">true</div> 351 <div id="pageData-showTOC" class="pageData">true</div>
352 352
353 <p>We want extensions to be autoupdated for some of the same reasons as Google C hrome itself: to incorporate bug and security fixes, add new features or perform ance enhancements, and improve user interfaces.</p> 353 <p>We want extensions to be autoupdated for some of the same reasons as Google C hrome itself: to incorporate bug and security fixes, add new features or perform ance enhancements, and improve user interfaces.</p>
354 354
355 <p>If you publish your extension using the <a href="https://chrome.google.com/we bstore/developer/dashboard">Chrome Developer Dashboard</a>, you can <em>ignore t his page</em>. You can use the dashboard to release updated versions of your ext ension to users, as well as to the Extensions Gallery or Chrome Web Store.</p> 355 <p>If you publish your extension using the <a href="https://chrome.google.com/we bstore/developer/dashboard">Chrome Developer Dashboard</a>, you can <em>ignore t his page</em>. You can use the dashboard to release updated versions of your ext ension to users, as well as to the Chrome Web Store.</p>
356 356
357 <p>If you want to host your extension somewhere other than the gallery or store, keep reading. 357 <p>If you want to host your extension somewhere other than the store, keep readi ng.
358 You should also read <a href="hosting.html">Hosting</a> and 358 You should also read <a href="hosting.html">Hosting</a> and
359 <a href="packaging.html">Packaging</a>.</p> 359 <a href="packaging.html">Packaging</a>.</p>
360 360
361 361
362 <a name="H2-0"></a><h2>Overview</h2> 362 <a name="H2-0"></a><h2>Overview</h2>
363 <ul><li>An extension manifest may contain an "update_url" field, pointing to a l ocation for doing update checks.</li> 363 <ul><li>An extension manifest may contain an "update_url" field, pointing to a l ocation for doing update checks.</li>
364 <li>The content returned by an update check is an <em>update manifest</em> XML d ocument listing the latest version of an extension.</li></ul> 364 <li>The content returned by an update check is an <em>update manifest</em> XML d ocument listing the latest version of an extension.</li></ul>
365 365
366 <p>Every few hours, the browser checks whether any installed extensions have an update URL. For each one, it makes a request to that URL looking for an update m anifest XML file. If the update manifest mentions a version of an extension that is more recent than what's installed, the browser downloads and installs the ne w version. As with manual updates, the new <code>.crx</code> file must be signed with the same private key as the currently installed version.</p> 366 <p>Every few hours, the browser checks whether any installed extensions have an update URL. For each one, it makes a request to that URL looking for an update m anifest XML file. If the update manifest mentions a version of an extension that is more recent than what's installed, the browser downloads and installs the ne w version. As with manual updates, the new <code>.crx</code> file must be signed with the same private key as the currently installed version.</p>
367 367
(...skipping 322 matching lines...) Expand 10 before | Expand all | Expand 10 after
690 _uff=0; 690 _uff=0;
691 urchinTracker(); 691 urchinTracker();
692 } 692 }
693 catch(e) {/* urchinTracker not available. */} 693 catch(e) {/* urchinTracker not available. */}
694 </script> 694 </script>
695 <!-- end analytics --> 695 <!-- end analytics -->
696 </div> 696 </div>
697 </div> <!-- /gc-footer --> 697 </div> <!-- /gc-footer -->
698 </div> <!-- /gc-container --> 698 </div> <!-- /gc-container -->
699 </body></html> 699 </body></html>
OLDNEW
« no previous file with comments | « no previous file | chrome/common/extensions/docs/faq.html » ('j') | chrome/common/extensions/docs/packaging.html » ('J')

Powered by Google App Engine
This is Rietveld 408576698