@Ayespy and @mib2berlin, thanks. It helps me to develop a strategy . Only have a dual boot Windows and Linux desktop, and a Windows 10 laptop. I dare not think of more, although I am tempted to build a small separate Linux box.
Edit: The video was updated to fix some typos and improve some notes.
A brief tutorial on customising Vivaldi.
There is no sound. Pause the video if you need more time to read the comments, and want to try out the tips for yourself.
Note: If you want to comment on the video, please comment under the video and not here to avoid disrupting this thread.
It's pretty standard behavior for browsers. The font options in your browser settings effect pages that don't have fonts definitions locked down as @barbudo2005 described. This is pretty important for web developers to have this kind of control. If you change the font for certain pages you'll significantly damage the page such that how to use it is no longer obvious -- buttons & other controls disappear and are replaced by a meaningless box.
The font you choose in the settings will apply to some pages where this kind of thing isn't a concern. For example, the font you set will be what is used to display Wikipedia's pages.
If you want to override fonts on pages that don't use the fonts in your settings, that requires a bit more work, as it should. The issue with just having a font option in the main settings that can override every single page is that it exposes many, perhaps even most, users to broken pages that they don't understand how to fix. People that know how to override fonts for every page are far more likely to understand the risks, and be able to identify when their font override is breaking the page and know how to fix it. For the (likely) majority of users, they would just think that Vivaldi breaks the page and is unable to display many websites, negatively impacting the browser's reputation.
So, if you want to override the fonts on sites that don't use the browser settings, you can do so easily by using an extension like Stylus. This is what I use, and am able to choose a font from a dropdown in the extension's popup dialog on the fly (changes the font without reloading the page). If you go down this road, keep in mind that doing this can break pages, and when you see broken pages try disabling your style to fix it.
I like it. So far seems to work okay, in v3.1.
One small visual problem: the text is blurry while it animates.
I too wouldn't mind being able to configure the colors/CSS, and the degree of darkening.
For example, in Opera 12 the focused text is also surrounded by a stylized border, which helps make it stand out even more.
@laimo You can add Ecosia as your Home page in Settings, General, if that is what you mean. Just copy and paste the URL.
What is your mother-tongue. There may be a local forum where you can post in your own language. It is hard to understand your English. A Bing translation may help.
@Pesala thanks for the hint!
In the meantime I've found https://forum.vivaldi.net/topic/24650/make-pinned-tabs-identifiable-when-using-vertical-tab-bar/6 which seems to work reasonably well on first glance.
Thanks and cheers,
Hi, it’s pretty much your choice if and how you use profiles. It depends on whether you want everything the same (in this case, stick with a single profile and use windows, stacks or sessions as already said) or if you prefer to have different settings per topic (in this case, profiles is what you want).
Can we somehow disable paid completion entries?
It isn't paid, it's just Autofill enabled at Address Field Settings, common behavior of most web browsers.
If it appears in the autocomplete suggestions drop-down you can identify from where it comes from (bookmarks, history or typed history) and delete it with Shift+Del.
You can read about how Vivaldi makes money here: https://vivaldi.com/blog/vivaldi-business-model/
We are mixing oranges and apples here.
Vivaldi doesn't make anything like Presto, a JS engine or other browser components so it doesn't compare with old Opera. Vivaldi could chose to add a GUI to Firefox code but they chose Chrome/Chromium because back then the code was more modern and easier to deal with compared to then aging Firefox.
When developing Web sites you have two options.
You stay "conservative" and use only "standard" stuff that you know works everywhere or you push to the limit knowing you are going to full support just some niche, usually the most common configuration, once it was Windows + IE nowadays I guess it is Windows + Chrome and Android + Chrome. My own bank Web site doesn't work with anything but Chrome for example.
It NEVER depends on the browser because developers can always test their stuff and find a workaround for issues, at least in the 99% conditions.
The real issue works in reverse. Chrome being the "standard-de-facto" means Google can decide how the Internet must be made. There aren't many developers and even less customers who chose to struggle to maintain "neutrality" for the sake of the Internet and everybody.