summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorawatson@chromium.org <awatson@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-05-07 01:52:45 +0000
committerawatson@chromium.org <awatson@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-05-07 01:52:45 +0000
commit19ff1b5effd3d932185afadfc092e28146a4177c (patch)
treec805380a9451e283a17428df4ffe2597935bc56a
parentd4df382faab706f9a58a4d3c2215df13c73dfaf4 (diff)
downloadchromium_src-19ff1b5effd3d932185afadfc092e28146a4177c.zip
chromium_src-19ff1b5effd3d932185afadfc092e28146a4177c.tar.gz
chromium_src-19ff1b5effd3d932185afadfc092e28146a4177c.tar.bz2
Removed reference to whitelisting requirement.
BUG= R=kalman@chromium.org, petewil@chromium.org Review URL: https://codereview.chromium.org/14909003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@198590 0039d316-1c4b-4281-b951-d872f2087c98
-rw-r--r--chrome/common/extensions/docs/templates/articles/cloudMessaging.html15
1 files changed, 2 insertions, 13 deletions
diff --git a/chrome/common/extensions/docs/templates/articles/cloudMessaging.html b/chrome/common/extensions/docs/templates/articles/cloudMessaging.html
index 62392be..9adc43c 100644
--- a/chrome/common/extensions/docs/templates/articles/cloudMessaging.html
+++ b/chrome/common/extensions/docs/templates/articles/cloudMessaging.html
@@ -119,7 +119,7 @@ to use the push messaging service
<code>onMessage</code> event.</li>
</ul>
</li>
- <li>Publish and get whitelisted. </li>
+ <li>Publish your app in the Chrome Web Store. </li>
<li>Use refresh token to get a valid access token.</li>
<li>Send message to user.</li>
</ol>
@@ -290,18 +290,13 @@ The app or extension need not be running when the message arrives;
the handler can be registered after the message arrives.
</p>
-<h2 id="store">Publish and get whitelisted</h2>
+<h2 id="store">Publish your app</h2>
{{^is_apps}}
<p>
To use the push messaging service,
you must publish your extension in the
<a href="https://developers.google.com/chrome/web-store/docs/get_started_simple">Chrome Web Store</a>.
-Your extension must also be whitelisted.
-To be added to the whitelist,
-please email
-<a href="mailto:gcm-for-chrome-whitelist@google.com">gcm-for-chrome-whitelist@google.com</a>
-with your extension ID and we will reply appropriately.
</p>
{{/is_apps}}
@@ -310,11 +305,6 @@ with your extension ID and we will reply appropriately.
To use the push messaging service,
you must publish your app in the
<a href="https://developers.google.com/chrome/web-store/docs/get_started_simple">Chrome Web Store</a>.
-Your app must also be whitelisted.
-To be added to the whitelist,
-please email
-<a href="mailto:gcm-for-chrome-whitelist@google.com">gcm-for-chrome-whitelist@google.com</a>
-with your app ID and we will reply appropriately.
</p>
{{/is_apps}}
@@ -445,7 +435,6 @@ Here's a brief summary of the push messaging errors:
<li>Payload is too long (must be 256 bytes or less).</li>
<li>Daily message quota exceeded (10,000 message requests allowed per day).</li>
<li>Google Account calling the push messaging service does not own the app or extension.</li>
- <li>App or extension is not whitelisted.</li>
<li>An internal error has occurred.
This indicates something went wrong on the Google server side
(for example, some backend not working