Advice Request The best experimental flags for Microsoft Edge (edge://flags)

  • Thread starter Thread starter ForgottenSeer 85179
  • Start date Start date
Please provide comments and solutions that are helpful to the author of this topic.
  • Like
  • Thanks
Reactions: Gandalf_The_Grey, ForgottenSeer 85179 and Protomartyr
oldschool said:
This was integrated by default not long after the introduction of Edge Chromium so the flag was superfluous quite some time ago.
Click to expand...
Good to know!

Also i found this new flag:
Application Guard Prelaunch
If enabled, Microsoft Edge Application Guard will be prelaunched in the background when recently used. – Windows
Click to expand...
#edge-wdag-prelaunch
 
  • Like
Reactions: Gandalf_The_Grey, Jan Willy, CyberTech and 2 others
Tip: DON'T enable this flag if you watch videos in the new Chromium Edge

For a few weeks, I had a bug where I couldn't play any video content in MSEdge, and thought it was just because I was on the canary channel. I thought the bug would resolve itself, but after a while, I realized that something must be wrong as I was the only one experiencing the bug.

After thinking about it some more, and getting really fed-up that I couldn't watch videos of any sort (from Reddit, YouTube, Twitter, etc), I decided to look at the flags I had enabled to see if any of them were causing the issue, and low and behold, disabling this one did the trick.

If you like to enable flags to test new features: DON'T ENABLE THIS ONE! Something about it ruins Edge's ability to play video content, and just shows a black screen instead of the video.

If you know what it does, or you're testing the flag, power to you! Otherwise, just stay away from it. ;)

Enjoy the new Edge experience! I'm excited to see these new vertical tabs.... Seems like an interesting idea....
Click to expand...
#edge-mf-clear-playback-win10
 
  • Like
Reactions: Protomartyr, silversurfer, Gandalf_The_Grey and 3 others
edge://flags/#cross-origin-opener-policy
Also available in Brave release channel.

Cross-Origin-Opener-Policy (COOP) header - HTTP | MDN

The HTTP Cross-Origin-Opener-Policy (COOP) response header allows a website to control whether a new top-level document, opened using Window.open() or by navigating to a new page, is opened in the same browsing context group (BCG) or in a new browsing context group.
developer.mozilla.org developer.mozilla.org
 
Last edited:
  • Like
  • Thanks
Reactions: Protomartyr, ForgottenSeer 85179, SeriousHoax and 3 others
I reset #same-site-by-default-cookies because that's now default with Edge 86 (y)

SameSite=Lax Cookies By Default. To improve web security and privacy, cookies will now default to SameSite=Lax handling by default. This means that cookies will only be sent in a first-party context and will be omitted for requests sent to third-parties. This change can cause compatibility impact on websites that require cookies for third-party resources to function correctly. To permit such cookies, web developers can mark cookies which should be set from and sent to third-party contexts by adding explicit SameSite=none and Secure attributes when the cookie is set. Enterprises that wish to exempt certain sites from this change can do so using the LegacySameSiteCookieBehaviorEnabledForDomainList policy, or can opt-out of the change across all sites using the LegacySameSiteCookieBehaviorEnabled policy.
Click to expand...
 
  • Like
  • +Reputation
Reactions: oldschool, Protomartyr, silversurfer and 1 other person
Sorry just being lazy, are any of these setting now default?

#Anonymize local IPs exposed by WebRTC.
#extension-content-verification (strict)
#reduced-referrer-granularity
#disallow-doc-written-script-loads
#enable-mark-http-as (unsecure)
#enable-lazy-image-loading
#enable-lazy-frame-loading
#strict-origin-isolation
#enable-heavy-ad-intervention
#raw-clipboard (disabled)

Thanks in advance (@knowledgable members of this forum :) )
 
Last edited:
  • Like
Reactions: oldschool, Protomartyr and Gandalf_The_Grey
#Anonymize local IPs exposed by WebRTC
Click to expand...
Not available anymore

#reduced-referrer-granularity
#enable-lazy-image-loading
Click to expand...
available but not needed

#raw-clipboard
Click to expand...
available, unsure about if it is good or not

#extension-content-verification (strict)
#disallow-doc-written-script-loads
#enable-mark-http-as (unsecure)
#enable-lazy-frame-loading
#strict-origin-isolation
#enable-heavy-ad-intervention
Click to expand...
available and still important
 
  • Like
  • Thanks
Reactions: oldschool, Protomartyr, silversurfer and 3 others
Thanks new list of enabled flags

Extension
  • Extension Content Verification (strict)
  • CORS for content scripts
  • Force empty CORB and CORS allowlist
  • Load Media Router Component Extension (disabled)
Security
  • Strict-Origin-Isolation
  • Block scripts loaded via document.write
Privacy
  • Heavy Ad Intervention
  • Heavy ad privacy mitigations
 
  • Like
  • +Reputation
Reactions: ANNOx, oldschool, Protomartyr and 4 others
security123 said:
available but not needed
Click to expand...
Any explanation on why #reduced-referrer-granularity is not needed anymore?
Lenny_Fox said:
Heavy ad privacy mitigations
Click to expand...
Looks like according to Edge it's on by default.
1.PNG
 
  • Like
  • Thanks
Reactions: ANNOx, oldschool, Protomartyr and 2 others
silversurfer said:
Flag: Anonymize local IPs exposed by WebRTC seems to be removed even on other chromium-based browsers...
Click to expand...
This one and some other familiar security/privacy flags have been removed or incorporated into browsers. I have only 4 or 5 in Brave and Edge.
 
  • Like
Reactions: harlan4096, SeriousHoax, Protomartyr and 1 other person

You may also like...