| Index: chrome/common/extensions/docs/extensions/contentSecurityPolicy.html
|
| diff --git a/chrome/common/extensions/docs/extensions/contentSecurityPolicy.html b/chrome/common/extensions/docs/extensions/contentSecurityPolicy.html
|
| index 7852ad3155c7e5af047f8589b2b326be89515ad8..e55979bbbe9108d27fee8dcd5e2fe567d4e3f155 100644
|
| --- a/chrome/common/extensions/docs/extensions/contentSecurityPolicy.html
|
| +++ b/chrome/common/extensions/docs/extensions/contentSecurityPolicy.html
|
| @@ -417,6 +417,12 @@ popup.html:
|
| <code>chrome-extension-resource</code>.
|
| </p>
|
| <p>
|
| + To ease development, we're also allowing the whitelisting of resources loaded
|
| + over HTTP from servers on your local machine. You may whitelist script and
|
| + object sources on any port of either <code>http://127.0.0.1</code> or
|
| + <code>http://localhost</code>.
|
| +</p>
|
| +<p>
|
| A relaxed policy definition which allows script resources to be loaded from
|
| <code>example.com</code> over HTTPS might look like:
|
| </p>
|
|
|