31–40 of 47 posts
I remember doing this expansion when I worked there: every module you include has its own set of command flags, and none get suppressed when you include them, so you end up with colossal unions like this. It's not as though any one team said, "Hey, let's have 1600 flags!"
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-…
I've tested 300+ of them for the purpose of reducing browser fingerprintability while building ArchiveBox's puppeteer support. It was quite a journey! Lots of subtle GPU rendering stuff that can easily give away a headless browser, or that differs between OS's in ways that can be used to detect when a browser doesn't match the expected behavior for the OS it reports to be running on. Some of my favorite lesser-known…
This could be a good thing. Too many applications are overly opinionated, make decisions on behalf of the user (without the ability to override), minimize user choice, don't respect the user's configuration, and in general, do things their way rather than the user's way. More switches is often better.
--false Value indicating whether flag from command line switch is false. So I can have fun with --false=true --true=false?
Former chromium dev here - I wouldn't be surprised if many of these are deprecated and just need to be cleaned up (removed from the codebase).
While testing, I noticed that some flags do nothing or contradict each other, but I wasn't sure if I was correctly using/understanding the flags.
I remember doing this expansion when I worked there: every module you include has its own set of command flags, and none get suppressed when you include them, so you end up with colossal unions like this. It's not as though any one team said, "Hey, let's have 1600 flags!"
But, apparently, no one has said "Hey, let's not have 1600 flags", either.
Getting rid of anything that's already out there. Someone, somewhere, is using it.
Google's apparently mastered that art, at least.
My favorite is the one that disables CORS... makes it easy to write local clients/tools that can get data from anywhere: --disable-web-security
I also found this extension to be useful and more configurable: https://chromewebstore.google.com/detail/allow-cors-access-c...
My favorite is the one that disables CORS... makes it easy to write local clients/tools that can get data from anywhere: --disable-web-security
I also found this extension to be useful and more configurable: https://chromewebstore.google.com/detail/allow-cors-access-c...