Index: chrome/common/extensions/docs/templates/articles/hosting.html |
diff --git a/chrome/common/extensions/docs/templates/articles/hosting.html b/chrome/common/extensions/docs/templates/articles/hosting.html |
index eec00a05a5f7c8ba1611032ab5fdd1896a7d7b3f..058ed78b9aa951b84a8ee72945c6212e6bb62927 100644 |
--- a/chrome/common/extensions/docs/templates/articles/hosting.html |
+++ b/chrome/common/extensions/docs/templates/articles/hosting.html |
@@ -2,7 +2,7 @@ |
<p class="warning"><b>Warning:</b> |
As of Chrome 33, |
-Windows stable/beta channel users can only download extensions |
+Windows users can only download extensions |
hosted in the Chrome Web store, |
except for installs via |
<a href="https://support.google.com/chrome/a/answer/188453">enterprise policy</a> |
@@ -10,8 +10,9 @@ or |
<a href="getstarted#unpacked">developer mode</a> |
(see |
<a href="http://blog.chromium.org/2013/11/protecting-windows-users-from-malicious.html">Protecting Windows users from malicious extensions</a>). |
-You can still create your own <code>.crx</code> file and use it for testing in the dev channel, |
-but you can't host that file on your own server. |
+As of Chrome 44, no external installs are allowed from a path to a local .crx on Mac |
+(see |
+<a href="http://blog.chromium.org/2015/05/continuing-to-protect-chrome-users-from.html">Continuing to protect Chrome users from malicious extensions</a>). |
</p> |
<p> |