Which vivaldi://flags do you use?
Hadden89 last edited by Hadden89
What are yours?
Of course, None is still a valid answer (and a excellent choice).
I'll do three list:
USEFUL (Known to enhance something in the browser)
- #extensions-on-chrome-urls (mod/dev)
- #enable-fast-unload (faster tab close, even accidentals ones)
- #save-page-as-mhtml (I love this format)
- #enable-devtools-experiments (mod/dev)
- #debug-packed-apps (mod/dev)
- #enable-experimental-web-platform-features (mod/dev)
- #enable-native-notifications (UI)
- #enable-message-center-new-style-notification (UI)
- #automatic-tab-discarding (hate auto hibernation)
- #proactive-tab-freeze-and-discard (to prevent tab hibernation)
- #extension-content-verification > enforce try to get.. (helps with some extensions)
- #PasswordExport | #PasswordImport (for backups/restores)
- #enable-mark-http-as > mark HTTP sites as insecure (will be default soon)
* #enable-ephemeral-flash-permission (set to disable): if you like to still store flash data on your browser (actually you shouldn't). Removed on chr71.
- chrome://flags#extension-active-script-permission: enable the new permissions platform (chr70. still in progress on V).
- chrome://flags/#enable-modern-media-controls (new html5 player is slightly changed
and quite ugly, disable for old layout).
DUBIOUS (Potentially placebos; may degrade performances)
- #autoplay-policy (ignored)
- #enable-site-settings (ui)
- #smooth-scrolling (never felt any difference)
- #enable-nostate-prefetch > enable prerender
* #memory-ablationRemoved on chr69?
- #enable-parallel-downloading (useful? on big files)
- #enable-picture-in-picture (is default behaviour now, no need to change it)
RISKY (Dropped due performance/function degradation)
- #enable-site-per-process (increase ram usage, security and may break captchas).
- #enable-quic (slowdown tab loading)
- #enable-simple-cache-backend (slowdown tab loading)
- (not available as flag) --enable-features="CheckerImaging"
Had severe glitches with it, so better avoid it (canary has it on)
- #ignore-gpu-blacklist (fix GPU/video issues OR cause issues if misused). Don't enable other gpu flags with this ON.
* #default-tile-width > 1024 (ram =>8gb)(removed on chr72)
* #default-tile-height > 1024 (ram =>8gb)(removed on chr72)
- #enable-zero-copy (gpu)
- #num-raster-threads > 4 (gpu)
* #gpu-rasterization-msaa-sample-count > 16 (gpu)(removed on chr72)
[GPU/RAM flags can easily degrade performance. Be aware of this]
@hadden89 I'm pretty cautious when it comes to flags, so my answer is none, unless absolutely needed. Flags typically enable code that's not stable enough for day-to-day use or enable features that should only be used under special circumstances. In some cases, they also revert old Chromium code if a new feature (e.g. new UI) has problems. Setting some flags can also (sometimes seriously) break Vivaldi. That said, there are a few flags that I've used or recommended with caution under some circumstances:
#ignore-gpu-blacklist is useful for Mac users. If the GPU has been blacklisted by the Chromium developers and hardware acceleration is disabled, Vivaldi currently won't be able to play H.264 and other proprietary media types. However, you need to use care when enabling this flag. If the GPU got blacklisted, it got blacklisted for a reason... typically to work around video driver bugs... so beware that enabling this flag could cause performance and rendering issues and (in rare cases) possibly even compromise the security of your system. Also, DO NOT enable any other graphics-related flags when enabling this flag.
#debug-packed-apps is useful for when you need to debug the Vivaldi UI
#PasswordExport and #PasswordImport - Enable when you need to export/import passwords and then revert these flags back to their defaults.
Lastly, if you're ever running into problems with Vivaldi, the first thing that you should do is reset all flags back to their defaults and retest before reporting any bugs.
@hadden89 I've used "save as MHTML" but not currently. So, None.
It's important as a tester and a mod to know what the browser is doing without any alterations, so that I know how it's designed to behave, and what the likelihood is that a user issue is native to the browser, or introduced by something related to user choices, or environmental (system and 3rd party software) factors.
This diagnostic baseline is also aided by the fact that I use no 3rd party software related to UI behavior, security, or manner of connecting to the internet.
Hmm, I just realized that I have switched the
#autoplay-policyto "Document user activation is required" some time ago, but it doesn't seem to do anything...
I used to run loads but cut back on the ones that change how the engine behaves to make sure any bugs i found were actually "real".
Some i do still use:
- debug packed apps, silent debugger for modding
- The 3 overlay scrollbars flags
- The flag that displays http as totally insecure
Hadden89 last edited by Hadden89
Yeah, test version hasn't any flags/mods on -- of course
Only main profile has them, but actually only some "core flags" (which are in useful list) seems to help; and of course I don't use GPU blacklist as my card seems to be totally HW accelerated (yay)
I have to admit that I haven't searched it that much, but:
Why being that Chromium is Newly Developed, the Flags aren't organized¿?
Some of them, now seems "Updated" and appears together, Global Media controls, Happiness...
But being that it was started from the beginning, not adapted, how would be this possible¿?