chromium/src
0
Fork 0
Code Activity

Fixup typo in configuration.md

Browse Source 
The command line for enabling a feature should be "--enable-features"
but not "--enable-feature".

Change-Id: I99878c6b968f094378687a094009c16166f53c77
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2832391
Auto-Submit: Owen Min <zmin@chromium.org>
Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#873434}
This commit is contained in:
Owen Min
2021-04-16 19:55:02 +00:00
committed by Chromium LUCI CQ
parent e9cc025540
commit 3e52abb9ff
1 changed files with 1 additions and 1 deletions

2
docs/configuration.md

@ -31,7 +31,7 @@ Example: base::kDCheckIsFatalFeature
These are implemented via creating a [base::Feature][base-feature] anywhere.
These can be enabled via server-side experimentation or via the command-line
using --enable-feature. Which features are in use is tracked by UMA metrics,
using "--enable-features". Which features are in use is tracked by UMA metrics,
and is visible in chrome://version as the "Variations" field. Do note that in
release builds, only a series of hashes show up in chrome://version rather than
the string names of the variations, but these hashes can be turned back into