There are command line flags (or "switches") that Chromium (and Chrome) accept in order to enable particular features or modify otherwise default functionality. Current switches may be found at http://peter.sh/examples/?/chromium-switches.html It is important to note that using these switches is not supported or recommended. They should only be used for temporary cases and may break in the future. Note that if you look at Windows
macOS
Linux
V8 FlagsV8 can take a number of flags as well, via Chrome's chrome.exe --js-flags="--trace-opt --trace-deopt --trace-bailout"
To get a listing of all possible V8 flags: chrome.exe --js-flags="--help" Browse the V8 wiki for more flags for V8. AndroidVisit ' If you are running on a rooted device or using a debug build of Chromium, then you can set flags like so: out/Default/bin/chrome_public_apk argv # Show existing flags. You can also install, set flags, and launch with a single command: out/Default/bin/chrome_public_apk run --args='--foo --bar' For production build on a non-rooted device, you need to enable "Enable command line on non-rooted devices" in about:flags, then set command line in /data/local/tmp/chrome-command-line, finally manually restart Chrome (restarting from about:flags page might no be enough to trigger reading this file). See https://crbug.com/784947. ContentShell on AndroidThere's an alternative method for setting flags with ContentShell that doesn't require building yourself:
adb shell am start \ -a android.intent.action.VIEW \ -n org.chromium.content_shell_apk/.ContentShellActivity \ --es activeUrl "http://chromium.org" \ --esa commandLineArgs --show-paint-rects,--show-property-changed-rects This will launch contentshell with the supplied flags. You can apply whatever commandLineArgs you want in that syntax. Chrome OS
|
For Developers > How-Tos >