Hello,
I can't seem to get items in chrome://flags that control variation parameters to work on ChromeOS. Here are three examples:
chrome://flags/#enable-mark-http-as
chrome://flags/#omnibox-ui-max-autocomplete-matches
chrome://flags/#omnibox-ui-vertical-margin
- In the ChromeOS on Linux build config:
- Nothing on about:flags seems to have any effect at all.
- But command line options force-fieldtrials and force-fieldtrial-params do work.
- On an actual Canary Chromebook:
- Almost everything on about:flags works, but none of the options controlled with FEATURE_WITH_PARAMS_VALUE_TYPE in about_flags.cc, like the three listed above, work. These are non-functional.
- Command line options force-fieldtrials and force-fieldtrial-params placed within /etc/chrome_dev.conf are reflected in chrome://version, but do not seem to have any effect.
- The actual Field Trial configuration derived from the Google Servers DOES seem to work! But if you set anything in about:flags (or in the command line), it disables the server-side field trial configuration, sets it to the default value, and ignores what's actually specified in about:flags or command line.
At this point I'm very confused and I thought i'd consult the experts...
Thanks,
Tommy