summaryrefslogtreecommitdiffstats
path: root/chrome/common/attrition_experiments.h
diff options
context:
space:
mode:
authorvadimt@chromium.org <vadimt@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-04-27 04:30:56 +0000
committervadimt@chromium.org <vadimt@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-04-27 04:30:56 +0000
commit3d6d11b2ddff36a0e032a9b5a68e1f51dccbc83d (patch)
tree657518e63a9eba594bc91833697661cc52c56ea2 /chrome/common/attrition_experiments.h
parentf34ff7dcb77d2dc0982e88bf8bf5b89a26ab3515 (diff)
downloadchromium_src-3d6d11b2ddff36a0e032a9b5a68e1f51dccbc83d.zip
chromium_src-3d6d11b2ddff36a0e032a9b5a68e1f51dccbc83d.tar.gz
chromium_src-3d6d11b2ddff36a0e032a9b5a68e1f51dccbc83d.tar.bz2
Switching to chrome.location API.
The location watch exists during the whole lifetime of the extension. It notifies the extension about changes in location. In addition, it gets reset before scheduled cards updates in order to explicitly retrieve location at these moments. BUG=164227 TEST=After getting new cards (see console output), immediately move to another location (you can drive between coffee houses, for example). You have to get to the new place and connect there faster than the suggested expiration_timestamp_seconds from the server. Say, if that time is X mins, you should move and connect in X/2 mins. Once you arrive and connect, make sure the cards appear faster than in X mins, and that they for the new location. P.S. The test is not a joke. This is an important scenario that needs to be tested. Review URL: https://chromiumcodereview.appspot.com/13966013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@196940 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/common/attrition_experiments.h')
0 files changed, 0 insertions, 0 deletions