Feature Request: Support Patching Unsupported Flag Ticker about chrome-developer-mode-extension-warning-patcher

[Ceiridge]

Try setting this policy/registry value to 0 first: https://chromeenterprise.google/policies/?policy=CommandLineFlagSecurityWarningsEnabled

[aaronliu0130]

I can't find the relevant policy key for edge.

[Ceiridge]

You will probably need to set it manually in the registry.
Maybe you can guess the registry path with the help of these resources:
https://admx.help/?Category=ChromeEnterprise&Policy=Google.Policies.Chrome::CommandLineFlagSecurityWarningsEnabled
https://docs.microsoft.com/en-us/deployedge/microsoft-edge-policies
HKLM\SOFTWARE\Policies\Microsoft\Edge -> CommandLineFlagSecurityWarningsEnabled (DWORD) = 0

[aaronliu0130]

There appears to be no HKLM\SOFTWARE\Policies\Microsoft\Edge keys

[Ceiridge]

Then create they registry key and try if it works.
HKLM means HKEY_LOCAL_MACHINE, maybe that's the issue?

[aaronliu0130]

Still doesn't work. Do I have to reboot or something?

The name is CommandLineFlagSecurityWarningsEnabled

[Ceiridge]

This policy normally should hide these warnings, but apparently it does not work (for Edge?).
I will potentially add a patch in the future

[Ceiridge]

Adding the command line flag --test-type should work. Tell me if there are other consequences

[aaronliu0130]

Sorry for the mail 2 days ago, that should've been sent out much earlier on Apr 12. Anyways yes that does solve the problem, but it isn't very convenient since I usually launch my apps from the taskbar, and windows 11 appears to lack the functionality of pinning short cuts. why did I upgrade

[Ceiridge]

Are you sure that you cannot pin a shortcut to taskbar by right-clicking on it, selecting Show more options and then clicking on Pin to taskbar?

[aaronliu0130]

Ooh, yes I can. There's a minor problem though. Windows doesn't think shortcuts with/without parameters are different and wouldn't let me pin the shortcut with a parameter without removing the old one.

[Ceiridge]

I took a look at the Chromium source code responsible for this information bar and found out that there is a policy that is supposed to disable it. That was months ago. Apparently Chromium ignores the policy.
Luckily, there is a command line argument that fixes this somehow.
If there is a policy or similar, no patches are needed

[aaronliu0130]

I'd like to know: which policy?

[Ceiridge]

This one:
#79 (comment)
Can be found here:
https://source.chromium.org/chromium/chromium/src/+/main:chrome/browser/ui/startup/infobar_utils.cc;l=37;drc=21a4c84dd469bfdc9f27375133dc309b62101ef8