We want to check how adding a component extension for Google Now affects browser startup time.
The only way to get a definitive answer is to check in a CL that enables the feature without a flag (in Canary) and let the bots cycle.
I'll also watch startup time histograms that come from the users who will install the build. After I get enough data, I'll back the change out.
The reason for commenting out "experimental" permission in the manifest is that I want the extension to start even without --enable-experimental-extension-apis flag.
While the experiment is running, Canary Chrome will load the Google Now component extension on startup. While Chrome is running, the extension will repeat the following every 5 min:
1. Get location of the computer. Sometimes this will result in a Wifi scan and sending a request to Google location-based services to get location. The location will not be sent back to Google, saved to disk or associated with the user.
2. Issue a XMLHttpRequest to a URL that turns to be a not existing local file. So, the request will fail every time.
BUG=164227
Review URL: https://chromiumcodereview.appspot.com/
12082061
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@180476 0039d316-1c4b-4281-b951-d872f2087c98