Disabling Field Trial experiments on Canary

[Kenneth Russell]

How can field trial experiments be disabled on Canary? We're facing a significant UI regression in Chrome (http://crbug.com/635724) that appears to be triggered by a field trial. Is there documentation on this? I couldn't find any after some quick initial searches. --disable-field-trial-config didn't seem to help.

Thanks,

-Ken

[Trent Apted]

In the past I've been able to use --user-data-dir=${HOME}/attempt1 , 2, 3, etc. to get a Chrome instance with the field trial disabled where a bug didn't repro. Then do a diff on the hashes in chrome://version to narrow it down.

Depending on the way the trial is configured

--disable-features=FooBar,BarBaz,...

or (typically for older things) something like

--force-fieldtrials=SiteIsolationExtensions/Enabled/

--force-fieldtrials=SiteIsolationExtensions/Control/

should force something on/off. But "Enabled" or "Control" could be other strings as well. E.g. "Enabled_Dogfood".

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

[Kenneth Russell]

Thanks Trent. After discussion with the field trials team I realized I'd used the wrong command line option to disable the experiments. Fixing this I was able to track down which experiment was causing the problem per http://crbug.com/635724 .

-Ken