List of Interesting Experimental Flags for Google Chrome to Try Out

[Sampei Nihira]

Also reduce the insecure cipher suites.
This Command Line Switch does not work in Chromium / Edge.
You can add to the command above the following line for Chrome.
The command line switch leaves only one insecure cipher suite active:

-cipher-suite-blacklist=0x002F,0x0035,0x000A,0x009C,0xC014,0x009D

Test

TLS Client Test - TLS Fingerprinting

Check your browser's supported SSL/TLS protocols. Inspect TLS ClientHello, supported cipher suites, TLS extensions, test ECH support. Identify weak or insecure options, generate a JA3/JA4 TLS fingerprint, and test how the browser handles insecure mixed content.

browserleaks.com

P.S.

If any of your websites not works, just start Chrome (from Start ) or enable a subsequent insecure cipher suite
You will notice that the command line switch following the previous one differs from the one proposed by the Peter Beverloo List.

 

[cryogent]

Its safe to enable this flags:

1 .Cookies without SameSite must be secure
-If enabled, cookies without SameSite restrictions must also be Secure. If a cookie without SameSite restrictions is set without the Secure attribute, it will be rejected. This flag only has an effect if "SameSite by default cookies" is also enabled. – Mac, Windows, Linux, Chrome OS, Android.

2. SameSite by default cookies
- Treat cookies that don't specify a SameSite attribute as if they were SameSite=Lax. Sites must specify SameSite=None in order to enable third-party usage. – Mac, Windows, Linux, Chrome OS, Android.


Find it in Brave.

 

[oldschool]

Its safe to enable this flags:

1 .Cookies without SameSite must be secure
-If enabled, cookies without SameSite restrictions must also be Secure. If a cookie without SameSite restrictions is set without the Secure attribute, it will be rejected. This flag only has an effect if "SameSite by default cookies" is also enabled. – Mac, Windows, Linux, Chrome OS, Android.

2. SameSite by default cookies
- Treat cookies that don't specify a SameSite attribute as if they were SameSite=Lax. Sites must specify SameSite=None in order to enable third-party usage. – Mac, Windows, Linux, Chrome OS, Android.


Find it in Brave.

Yes. And it's easy to revert if you were to run into a problem.

 

[cryogent]

Thank you

 

[Ink]

Try Chrome 84+ Heavy-Ads flags:

• chrome://flags/#enable-heavy-ad-intervention
• chrome://flags/#heavy-ad-privacy-mitigations see post below

Source: Handling Heavy Ad Interventions | Web | Google Developers

 

[oldschool]

Try Chrome 84+ Heavy-Ads flags:

• chrome://flags/#enable-heavy-ad-intervention
• chrome://flags/#heavy-ad-privacy-mitigations

Source: Handling Heavy Ad Interventions | Web | Google Developers

I believe the 2nd one is for debugging only.

 

[Sunshine-boy]

Hello, what happened to Enable AppContainer and Enable GPU AppContainer? Google removed both!

 

[oldschool]

Hello, what happened to Enable AppContainer and Enable GPU AppContainer? Google removed both!

It's been quite a while now.

 

[Lenny_Fox]

My Guess is that the AppContainer sandbox limitations provided problems for the recently updated file API. Some users might have noticed a new Site Permission called File editing.

Now the new API is implemented, the Q1 Quarterly update seems to hint on a revival of AppContainer.

Maybe Chromium developers/insiders can shed some light on this intriguing line of information.

 

[CyberTech]

Google launches Chrome extensions checkup experiment

Whether it is coincidence or a result of this report, Google has released a new experiment in Chrome 83 called 'Extensions Checkup'.

When enabled, this experiment will display information boxes at the top of the chrome://extensions page or as a small message at the bottom of New Tab Pages that try to educate users about the risks of using browser extensions.

To enable this experiment in Chrome 83, go to chrome://flags and search for 'extensions checkup'. When the experiment appears, you can select one of the 'Enabled' options to start displaying these educational alerts.

More information

New Google Chrome experiment warns of malicious and slow extensions

www.bleepingcomputer.com

 

[HarborFront]

New Extensions Menu Button

Starting with Chrome 83, all extensions are now managed through one single button on the Chrome toolbar, rather than having their own buttons. This is to save some real estate for the address bar. Users will still be able to pin their favorite extensions to the Chrome toolbar, but all newly installed extensions will first appear under the new extensions "puzzle" icon going forward.

Go to chrome://flags and enable Extensions Toolbar Menu

More new features in Chrome 83 here

Chrome 83 released with enhanced privacy controls, tab groups feature

Chrome 83 is one of the feature-rich Chrome releases in recent years.

www.zdnet.com

 

[Stas]

Go to chrome://flags and enable Extensions Toolbar Menu

It's enabled by default.

 

[CyberTech]

It's enabled by default.

No it's not i checked yesterday

 

[Stas]

No it's not i checked yesterday

If you set to disable "Extensions Toolbar Menu" disappears but if you set to enabled or default it appears, so it is enabled by default.

 

[CyberTech]

If you set to disable "Extensions Toolbar Menu" disappears but if you set to enabled or default it appears, so it is enabled by default.

Well I didn't do anything in Chrome even i dont use it i'm using Firefox atm i use chrome for test/check whats new in thats it when i see that new extensions as HarBor posted it i thought i would check in Chrome it says its up to date i didn't see the toolbar menu so i went to the flags list it says its disabled i had to enable it....

 

[HarborFront]

If you set to disable "Extensions Toolbar Menu" disappears but if you set to enabled or default it appears, so it is enabled by default.

Not in Brave browser. I checked in Default it's not enabled. I need to Enable it

 

[Stas]

Not in Brave browser. I checked in Default it's not enabled. I need to Enable it

Yes in Brave it's disabled by default but in Chrome it's enabled by default. I don't really see the need for it unless you want to hide extensions.

 

[HarborFront]

Yes in Brave it's disabled by default but in Chrome it's enabled by default. I don't really see the need for it unless you want to hide extensions.

If you have many extensions you can hide those which does NOT show blocking indicators. eg I don't care about cookies, Keyboard Privacy etc. Examples of those extensions which show blocking are uBO, ClearURLS, Decentraleyes etc. and those you need to fiddle (eg Dark Reader) you can leave them on the toolbar. It's similar to a built-in feature in FF whereby those addons WITHOUT blocking indicators can be moved to be hidden in a drop down menu.

If you only have 4 or 5 extensions then you don't need this flag

 

[Stas]

If you have many extensions you can hide those which does NOT show blocking indicators. eg I don't care about cookies, CSS Exfil Protection, Keyboard Privacy etc. Examples of those extensions which show blocking are uBO, ClearURLS, Decentraleyes etc. and those you need to fiddle (eg Dark Reader) you can leave them on the toolbar. It's similar to a built-in feature in FF whereby those addons WITHOUT blocking indicators can be moved to be hidden in a drop down menu.

If you only have 4 or 5 extensions then you don't need this flag

Like I said unless you want to hide extensions. All my extensions has blocking indicators except h264ify so it's useless for me, and CSS Exfil Protection has blocking indicator.

 

[HarborFront]

Like I said unless you want to hide extensions. All my extensions has blocking indicators except h264ify so it's useless for me, and CSS Exfil Protection has blocking indicator.

Yup, you are right about CSS Exfil Protection which can be tested below

CSS Exfil Vulnerability Tester

This page tests to see if your browser is vulnerable to Cascading Style Sheets (CSS) data leakage. If you are vulnerable, one way to protect yourself is to install the CSS Exfil Protection plugin for your browser.

www.mike-gualtieri.com

Above post edited