Add Args

[neoOpus]

Hi,

Please make it possible to add some args (by adding another field) that could be used for Chrome Flags and other command-line switches that are necessary in many cases for Devs.

Example of what I use for MS Edge

Example 1 :
--profile-directory=Default --max-old-space-size=61440 --disable-extension-activity-logging --enable-features=msEdgeAVIF,RawDraw,DrDc,UseSurfaceLayerWithDirectComposition,CanvasOopRasterization,msEdgeAVIF,WebUITabStrip,AsyncDns,BlocklistGpuModes,ChromeLabs,CustomizeChromeSidePanel,DeferredShaping,DesktopDetailedLanguageSettings,HistoryClustersOnDeviceClustering,Journeys,JourneysKeywordFiltering,JourneysLabel,JourneysOmniboxAction,JourneysOmniboxHistoryClusterProvider,JourneysOnDeviceClusteringContentClustering,OmniboxPedalSuggestions,OptimizedReadabilityDetection,PageContentAnnotations,ParallelDownloading,Portals,PortalsCrossOrigin,PostQuantumCECPQ2,Prerender2,PrivacyGuide2,QuickCommands,SanitizerAPI,SearchWebInSidePanel,SidePanelImprovedClobbering,SidePanelJourneys,SideSearch,SplitLargeText,TabGroupsSave,TabSearchFuzzySearch,UnifiedSidePanel,UseFlutterBalloons,UseSuggestEndingsApi,VariableCOLRV1,Vp9kSVCHWDecoding,WebBluetoothNewPermissionsBackend,WebBundles,WebShare,WebUsbDeviceDetection,sdch3

Example 2 :
--profile-directory=Default --no-experiments

Example 3 :
--profile-directory=Default --disable-extensions-except

But what would be amazing and maybe too much to ask is to have it fetch the flags from a curated online list or maybe added as a file that contains the various flags for chromium and also the derivative browsers, it could be a checkbox based with some basic (grouping, search, naming, etc) to allow testing, debugging and setting preferences who are optimal for specific hardware, user liking and scenarios (url, nat, www, etc)

I hope both make sense to you and inspire you,

Thank you.

[aloneguid]

I think this is a great idea, thank you. I'll get to this soon.
By the way you can do this in the meantime manually editing confiig.ini (find it from File menu) but arguments will be overwritten on rediscovery. You can also add a custom browser from UI from File menu, but it's not quite as pretty as you want.

[neoOpus]

Amazing, yeah I figured out that I can use the config.ini to do just than but it is not as practical as doing via GUI and yeah the rediscovery re-add some entries that I deleted from the config.ini (other browser selector that I was testing who are identified as Broswer by BT) maybe adding a way to exclude some directories or "Browsers" would be a good addition too.

[neoOpus]

let me know if I can help brainstorming how the UI should look like or maybe doing some wireframe suggestions

[aloneguid]

Yes please! I think this should be an "advanced" feature not polluting the main UI, maybe a popup window etc. I used a list of switches in the past from here which can be parsed using some script.

Flags will probably be applicable only on first browser launch.

[neoOpus]

Hi,

I understand your concern, it could be just a tiny drop down menu on the side of the Args field that allow to configure and pick the flags (that are predefined and saved), another popup window will allow to pick them and save them in a named "group"

Yes Peter's website is the go to for finding some of the chromium but most browser also have their own set of flags (Edge, Brave, Yandex, Vivaldi, etc), so maybe it should be a good idea to let end-users add them via copy/paste but what would be better and much more complex project is to create an alternative to Peter's page that is maintained by the commmunity of the most useful and valid flags that anyone can download and pick from a list with description of each one and comments (but that's maybe too complex).

You are right flags applies only on the first launch of the browser and all other instances (profiles) will use that too (it is a bad thing if you ask me but that's how Chromium is designed)…

The reason I am asking you about this because all the browser keep the same default chromium experiment page, it is hard to keep track of the flags there and isolate those who are causing some issue that are not obvious immediately or you are not just testing them specifically like Quality Engineer would do, some flags allow to get a bit more of the browser than the default setting, enable some disabled by default features and hardware acceleration… so it make sense to have something to manage them and allow more people to play with them with ease.

[aloneguid]

I've been looking more closely and it seems like a complex project if implemented properly. I am not sure I have capacity to do this for so many browsers. Even if led by community, needs a way to coordinate all of it. It's worth keeping on a roadmap though.

[neoOpus]

No worries, I perfectly understand! I will keep suggesting features if you don't mind who are less complex to implant.

Thank you again for what you are doing