I don't use a dark theme at all, but from my understanding, Vivaldi is still a pretty small development team and might be willing to make the necessary changes for you to have your preferred dark theme. They have a section on their forum for requests and they cover in depth on how to request a feature here.

You could also try messaging forum member ruario to see if he can have any sway with the UI/UX team (not even sure what team he belongs to with the browser).

1 members found this post helpful.

Thanks!

I'll pm ruario and see if he could possibly sway the team to consider a dark theme for FF.

Not Firefox, he works for Vivaldi.

Got it:-

This script for FF was made by ruario too:

https://gist.github.com/ruario/9672798

Provided I can find the next version of Chromium in a rpm format I can convert it with rpm2tgz and use installpkg to install it.

rpm2tgz
One of the most ubiquitous package formats for Linux software is RPM; it's not uncommon to find a developer offering their application for download as either source code or an RPM file, and no more. In this case, you would have three options:

Build your own Slackware package.
Compile and install directly from source code.
Convert and install from RPM.
Building from source code or creating your own Slackware package is usually not as complex as you might think but installing directly from source code is generally discouraged because there is no easy way to track what has been installed on your system after issuing the make install command. Building your own Slackware packages is outside the scope of this chapter. So this leaves us with the helpful tool rpm2tgz.

rpm2tgz converts RPM packages into a Slackware package that can then be installed via pkgtool or installpkg. This circumvents the need to create your own Slackware package but grants you the benefit of being able to remove, update, and track what you've installed.

https://docs.slackware.com/slackbookackage_management

I knew about rpm2tgz but forgot about it since I never needed to use it.

After downloading notepad .rpm and converting it to a tgz I installed it.
Later I removed it with removepkg.

I'm hoping that I can do this with the .rpm of Chromium.

If it fails I've already found out that the dependencies have to be resolved first before converting to a tgz.

Installing the newest version of Chromium form Eric's Slackware repo is the easiest solution so far.

http://www.slackware.com/~alien/slackbuilds/chromium/

Haven't had time to compile from src yet:-

Went to http://www.slackware.com/~alien/slackbuilds/chromium/ and downloaded the latest. Ran the command
# upgradepkg --install-new chromium-84.0.4147.94-x86_64-1alien.txz
and everything went perfectly, no error messages, Chromium started perfectly except Chromium doesn't connect to any web pages now. Blank white screen. I'm here reporting this on an old Firefox still surviving from the installation disc. I decided to try to upgrade Chromium because a lot of web sites have changed their code to take advantage of features on newer browsers, and installation Chromium wasn't cutting it. Was jumping from Chromium 56 or whatever straight to 84 too great a leap? Was 84.0.4147.89 working a few days ago and .94 not? I'd read Alien Bob's blog mentioning the release to slackbuilds of the first, and the sudden release by Google of the second. https://alien.slackbook.org/blog/chr...for-slackware/

I've been using Slackware since 1995, when you had to put your monitor's refresh rates into an .rc file, and everyone compiled their own kernels. Things have gotten so good that I haven't had to compile software in over a decade, and now I have no idea what to do with a program that doesn't work. I'm going to put together another computer and install something a bit more newbie friendly, say Mint, so I have something running for when I do something horrible to this machine trying to get Chromium running again.

balloo

If you installed Chromium on Slackware 14.2 just be sure to also update that Slackware 14.2 with all the latest patches provided online. Some updated packages (like mozilla-nss) are required for my own packages to function. On an un-patched out of the box Slackware 14.2 many of my packages for 14.2 will simply not function.

Nothing to do with Chromium. Alien Bob's chromium-84.0.4147.94 is working for me on Slackware64 14.2, and That's the Way (I Like It) - which is what I'm listening to and watching on Youtube on Chromium, one of the first things I do after I update Chromium to check if everything is working.

Sorry, I can't give you advice. Try what Alien Bob suggested.

TKS