Make --force-fieldtrials not activate them in the browser process.
This is to make this testing flag more consistent with what happens
with a server-side field trial, so that the field trial doesn't
appear in about:version until client code explicitly queries its
state via a group() call.
Does not change the behaviour of the --force-fieldtrials flag
when passes to the renderer process, where it does need to
activate the trials so that they show up in crash reports, etc.
BUG=255142
TEST=Start a debug build of Chrome with the command line
flag --force-fieldtrials=Bat/Man/ and check that it doesn't
show up in chrome://version.
Review URL: https://chromiumcodereview.appspot.com/17945002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@209795 0039d316-1c4b-4281-b951-d872f2087c98
CrOS-Libchrome-Original-Commit: cd36c6e67313d9a1b21f6c5806dfab527778f1e8
3 files changed