It's actually even more. --enable-features takes a list of features, and --force-fieldtrials takes a list of field trials. And each argument of --enable-features can itself have "sub-features", so you can have syntax like --enable-features=CoolFeature:Widget/1/Bells/cow*
I don't know if the syntax for all of this is actually documented anywhere, but anything in chrome://flags seems to be plumbed through via --enable-features. You can see the syntax in chrome://versions?show-cmd-variations.
It would be cool if someone updated the autogen table to also include the list of available features and field trials.
I didn't know that's where the feature flags lived. I imagine documenting them is tough because it'll heavily depend on the version since they graduate to become standard features over time.
I don't know if the syntax for all of this is actually documented anywhere, but anything in chrome://flags seems to be plumbed through via --enable-features. You can see the syntax in chrome://versions?show-cmd-variations.
It would be cool if someone updated the autogen table to also include the list of available features and field trials.