diff options
| author | pvalenzuela@chromium.org <pvalenzuela@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-12-06 10:26:35 +0000 |
|---|---|---|
| committer | pvalenzuela@chromium.org <pvalenzuela@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-12-06 10:26:35 +0000 |
| commit | 3db00dbf54c2b10f3735192d02991d4c44fab17b (patch) | |
| tree | 9f62cae597f65e56ba12413a938fe98032f7b664 /components/webdata.gypi | |
| parent | 7db2949ca2537039dbd798a4c48bf11a84c13c30 (diff) | |
| download | chromium_src-3db00dbf54c2b10f3735192d02991d4c44fab17b.zip chromium_src-3db00dbf54c2b10f3735192d02991d4c44fab17b.tar.gz chromium_src-3db00dbf54c2b10f3735192d02991d4c44fab17b.tar.bz2 | |
Add an HTML page to the Sync test server to trigger synced notifications
This change also fixes a bug where AddSyncedNotification
returned a binary-encoded string instead of ASCII.
Directions for triggering synced notifications in test server (Linux):
1) Build and run the test server:
ninja -C out/Debug run_sync_testserver
out/Debug/run_sync_testserver --port=1337
2) Run the browser against the test server:
google-chrome --enable-logging --enable-synced-notifications \
--sync-url=http://127.0.0.1:1337/chromiumsync
3) Go to browser settings. If you are already signed in, click
"Set up sync..." and hit OK on the subsequent dialog. Otherwise, sign in
and complete Sync setup.
4) Navigate to http://127.0.0.1:1337/syncednotifications and follow the
directions on the page.
BUG=248332
Review URL: https://codereview.chromium.org/100053007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@239159 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'components/webdata.gypi')
0 files changed, 0 insertions, 0 deletions