OLD | NEW |
1 <div id="pageData-name" class="pageData">Autoupdating</div> | 1 <h1>Autoupdating</h1> |
2 <div id="pageData-showTOC" class="pageData">true</div> | 2 |
3 | 3 |
4 <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> | 4 <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> |
5 | 5 |
6 <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> | 6 <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> |
7 | 7 |
8 <p>If you want to host your extension somewhere other than the store, keep readi
ng. | 8 <p>If you want to host your extension somewhere other than the store, keep readi
ng. |
9 You should also read <a href="hosting.html">Hosting</a> and | 9 You should also read <a href="hosting.html">Hosting</a> and |
10 <a href="packaging.html">Packaging</a>.</p> | 10 <a href="packaging.html">Packaging</a>.</p> |
11 | 11 |
12 | 12 |
(...skipping 127 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
140 <p>As we add more APIs to the extensions system, it's possible you will want to
release an updated version of an extension that will work only with newer versio
ns of the browser. While Google Chrome itself is autoupdated, it can take a few
days before the majority of the user base has updated to any given new release.
To ensure that a given extension update will apply only to Google Chrome version
s at or higher than a specific version, you add the "prodversionmin" attribute t
o the <app> element in your update manifest. For example:</p> | 140 <p>As we add more APIs to the extensions system, it's possible you will want to
release an updated version of an extension that will work only with newer versio
ns of the browser. While Google Chrome itself is autoupdated, it can take a few
days before the majority of the user base has updated to any given new release.
To ensure that a given extension update will apply only to Google Chrome version
s at or higher than a specific version, you add the "prodversionmin" attribute t
o the <app> element in your update manifest. For example:</p> |
141 | 141 |
142 <pre><?xml version='1.0' encoding='UTF-8'?> | 142 <pre><?xml version='1.0' encoding='UTF-8'?> |
143 <gupdate xmlns='http://www.google.com/update2/response' protocol='2.0'> | 143 <gupdate xmlns='http://www.google.com/update2/response' protocol='2.0'> |
144 <app appid='aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa'> | 144 <app appid='aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa'> |
145 <updatecheck codebase='http://myhost.com/mytestextens
ion/mte_v2.crx' version='2.0' <b>prodversionmin='3.0.193.0'</b>/> | 145 <updatecheck codebase='http://myhost.com/mytestextens
ion/mte_v2.crx' version='2.0' <b>prodversionmin='3.0.193.0'</b>/> |
146 </app> | 146 </app> |
147 </gupdate> | 147 </gupdate> |
148 </pre> | 148 </pre> |
149 | 149 |
150 <p>This would ensure that users of this extension would autoupdate to version 2
only if they are running Google Chrome 3.0.193.0 or greater.</p> | 150 <p>This would ensure that users of this extension would autoupdate to version 2
only if they are running Google Chrome 3.0.193.0 or greater.</p> |
OLD | NEW |