About the chrome://settings/content page

[Kurabiye]

Are the changes we've made to the chrome://settings/content page effective? Or do we need to use the settings page? The features on the chrome://settings/content page are not available or detailed in the settings section. Since I'm a new user, it's important for me to know. As much as the Vivaldi settings menu provides the freedom to customize the browser, from what I've seen, there are shortcomings in detailed site settings and security settings. If I'm wrong about this and I haven't noticed these features, please let me know.

[Pesala]

@kurabiye said in About the chrome://settings/content page:

Are the changes we've made to the chrome://settings/content page effective?

Yes; I believe that most are effective. Many of the more obscure settings have not yet been made available in the Vivaldi Settings dialog. Site settings can be accessed from the Padlock icon. Spell-check settings can be accessed from the context menu in an edit box.

[SMCSS]

@pesala said in About the chrome://settings/content page:

Many of the more obscure settings have not yet been made available in the Vivaldi Settings dialog. Site settings can be accessed from the Padlock icon.

@pesala
Since, for some reason, browser devs feel that users are just too "simple-minded" to be able to use flags, I do hope that the obscure settings do show up in the future. (although leaving the flags alone would have been a simpler and better option)

I like granular control. VERY granular. I dislike devs deciding "user shouldn't need it because I don't" or some other such nonsense.

I am not a cookie cutter clone. I am an individual and I detest someone trying to put me in a box.

Granular control is okay as long as you have a place for new users to reset to defaults.

[luetage]

@smcss Flags are another matter altogether. These will never be incorporated into settings, they have a dedicated page. This topic is about combining Chrome settings and Vivaldi settings, which simply hasn’t happened yet. It is not about trying to safeguard users and babysit them, or a third of the privacy settings in Vivaldi native settings wouldn’t be available without operating some kind of experiment switch first. The settings which are available in Chrome but not in Vivaldi settings aren’t necessarily the obscure and “dangerous” ones, it’s a mixed bag really.