New Firedragon version!

drwxr-xr-x    - root  2 Jan 16:58  browser
drwxr-xr-x    - root  1 Jan 13:19  defaults
drwxr-xr-x    - root  2 Jan 16:58  distribution
drwxr-xr-x    - root  2 Jan 16:58  fonts
drwxr-xr-x    - root  1 Jan 13:19  gmp-clearkey
lrwxrwxrwx    - root 30 Oct  2023  native-messaging-hosts -> /usr/lib/mozilla/native-messaging-hosts
.rw-r--r--  505 root 30 Oct  2023  application.ini
.rw-r--r--  104 root 30 Oct  2023  dependentlibs.list
.rwxr-xr-x 651k root 30 Oct  2023  firedragon
lrwxrwxrwx    - root 30 Oct  2023  firedragon-bin -> ../../bin/firedragon
.rwxr-xr-x  28k root 30 Oct  2023  firedragon.cfg
.rw-r--r-- 2.3k root 30 Oct  2023  firedragon.overrides.cfg
.rw-r--r--  282 root 30 Oct  2023  firejail-fix.hook
.rwxr-xr-x  19k root 30 Oct  2023  glxtest
.rwxr-xr-x 500k root 30 Oct  2023  libgkcodecs.so
.rwxr-xr-x 383k root 30 Oct  2023  libipcclientcerts.so
.rwxr-xr-x  31k root 30 Oct  2023  liblgpllibs.so
.rwxr-xr-x 3.9M root 30 Oct  2023  libmozavcodec.so
.rwxr-xr-x 236k root 30 Oct  2023  libmozavutil.so
.rwxr-xr-x 4.1k root 30 Oct  2023  libmozgtk.so
.rwxr-xr-x 122k root 30 Oct  2023  libmozsandbox.so
.rwxr-xr-x 1.2M root 30 Oct  2023  libmozsqlite3.so
.rwxr-xr-x  10k root 30 Oct  2023  libmozwayland.so
.rwxr-xr-x 146M root 30 Oct  2023  libxul.so
.rw-r--r--  32M root 30 Oct  2023  omni.ja
.rw-r--r--  100 root 30 Oct  2023  platform.ini
.rw-r--r-- 3.2k root 30 Oct  2023  README.md
.rw-r--r--    0 root 30 Oct  2023  removed-files
.rwxr-xr-x  13k root 30 Oct  2023  vaapitest

That definitely is the issue. Should not be as far back as Oct.
The file you got is also 9kb too small, so really not the one to use here.

Now what does

paru -Qi firedragon

say?

1 Like

That color is way too light, but --in-content-page-color seems very very very close, so I will give that one a try. Tnx for pointing out the file! :smiley:

2 Likes

I have actually two or 3 times reinstalled the thing so… :slightly_smiling_face:

 ╭─ankur@ankur in ~ as 🧙 took 26s
 ╰─λ paru -Qi firedragon
Installed From  : None
Name            : firedragon
Version         : 11.7.1-10
Description     : Floorp fork build using custom branding & settings
Architecture    : x86_64
URL             : http://dr460nf1r3.org
Licenses        : MPL2
Groups          : None
Provides        : None
Depends On      : dbus  dbus-glib  ffmpeg  gtk3  libevent  libjpeg  libpulse  libvpx  libwebp  libxss  libxt  mime-types  nss  pipewire  ttf-font  zlib
Optional Deps   : hunspell-dictionary: Spell checking
                  libnotify: Notification integration [installed]
                  networkmanager: Location detection via available WiFi networks [installed]
                  profile-sync-daemon: Load the browser profile into RAM [installed]
                  pulseaudio: Audio support [installed]
                  searx: Searching the web using a locally running searX instance
                  speech-dispatcher: Text-to-Speech
                  whoogle: Searching the web using a locally running Whoogle instance
                  xdg-desktop-portal: Screensharing with Wayland [installed]
Required By     : None
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 263.00 MiB
Packager        : Garuda Builder <[email protected]>
Build Date      : Sunday 31 December 2023 06:11:08 PM
Install Date    : Tuesday 02 January 2024 08:46:29 PM
Install Reason  : Explicitly installed
Install Script  : No
Validated By    : None


 ╭─ankur@ankur in ~ as 🧙 took 685ms
 ╰─λ 

Is it possible Hyprland installs packages differently?
Every file dated Oct 30 should be dated Dec 31 at the minimum, including firedragon itself, but you show version 11.7.1, which is mind-boggling.

What terminal command did you input to install the package?

1 Like

Hm, I though it was about the background color?
Anyways, I see it’s set also in chrome://global/skin/in-content/common-shared.css and perhaps other places.
That may explain why I could not override it in userChrome.css (I checked that toolkit.legacyUserProfileCustomizations.stylesheets is true).
Gotta RTFM some more.
Do you know if there are variables set dynamically to the theme colors?
#20242c looks nice with the Nord colors but it’s still hardcoded, back to square one.

1 Like

It is. Except color #f7f7f7 is way too light.
I did find just now that --in-content-page-background is found elsewhere in the file and uses color #333333 (or #333 in some place) and THAT is the exact color.
So correct option, just not under the right section that I was. :smiley:

Yes I had the same issue, which is why I posted the question about this I was then pretty sure it was hard coded somewhere. And I think you find out where!

You can change most of those changed by Firefox Themes.
And then just a couple through userChrome, like:

.tab-close-button
.tab-close-button:hover
@media not (prefers-contrast)
.close-icon:hover
#tabs-newtab-button
#tabs-newtab-button:hover
.tabbrowser-tab:not([selected]):hover .tab-background
.tabbrowser-tab:not([selected]):hover label

There are most probably others but it gives an idea of those that are not hard coded.

1 Like

I just noticed this comment in that second css

 * TODO (emilio): Once color-scheme support is complete, perhaps we can
 * just replace most of these for system colors and remove all this
 * duplication (assuming we honor the preferred color scheme for
 * in-content privileged pages and plain-text documents). */

also, there would be others to be changed to match, like input fields background.
ah, and it’s set #333 with !important in the first one

2 Likes

Nice find! Let’s hope they will make it for System colors.

I think pretty much all of those with #333 and #333333 would need to be changed for Firedragon.

2 Likes

Please, this time make a blue version :smiley:

5 Likes

Facepalm. I was supposed to use userContent.css not userChrome.css.

:root {
  --in-content-page-background: #20242c !important;
}
2 Likes

I generally use

yay <package_name>

or

sudo pacman -S <package_name>

Can you follow the steps in Post #1?

1 Like

I told how I generally install packages , for floorp rebased firedragon , I just followed what is said in post one

1 Like

And you got no errors in the terminal when issuing sudo pacman -U firedragon(etc…)?

@dr460nf1r3 do you have an idea on this installation?

2 Likes

That works!
So the other ones (like History page background) can also be changed by that file by the user.
Or patched by us to follow Dr460nized’s theme by default.

Thanks so much @meanruse !

2 Likes

Given this tends to cause issues too many times, I’m unsure whether we should part ways with this one as default setting. I stopped counting how many times this was the actual issue :sweat_smile: It would still be there in the Assistant, so… :thinking:

@FGD this needs to be changed in future versions to accommodate the new home :face_with_hand_over_mouth:

I wonder whether the dark color of the sweet theme (the same one as the titlebar) would be a good fit :saluting_face: should be something we can handle via patches at source code level?

This is actually quite weird! Certainly -U should install the updated files :sweat_smile: maybe pacman debug logs could provide some insight about what’s happening here? (the -v or -d flag should do)

3 Likes

@Ankur There is another possibility, if you are willing, it would be to purge completely all firedragon refs/folders/files and install directly v11.7.1. I had to do that once and it was like a fresh install from ISO.
Of course, backup your profile and firedragon.cfg/firedragon.overrides.cfg. Not to re-use them but in case you rollback to v119.

I apologize if this is a hijacking of the topic :cold_sweat:
I noticed that octopi has a firedragon-next 11.61.3
What about that?

A total no touch, plz. No support at all is given for Firedragon-next. It was a failed attempt.

1 Like