Not sure if this is also true for KDE.

    • Petter1@lemm.ee
      2·
      2 hours ago

      I hate Firefox for not working with my themes like all other apps do… And there seems to be no browser that does.

    • foremanguy
      3·
      4 hours ago

      It’s not a little detail, it means that Firefox is more integrated into your OS

    • Leaflet@lemmy.worldOPEnglish
      24·
      12 hours ago

      True, although not in the same way. KDE is using its own GTK theme and uses ~/.config/gtk-3.0/gtk.css to override colors to the accent color. But this method is broken for sandboxed versions of Firefox since they can’t access ~/.config/gtk-3.0/gtk.css (though with flatpak you could create an override to allow it).

      I believe (and hope) Firefox is now following the standardized accent color portal for determining the accent color. If so, then this accent color change should work on Gnome, KDE, Pantheon, and other desktops that support the accent color portal. If true, then even sandboxed apps should follow the accent color without messing with the sandbox.

      • daggermoon@lemmy.world
        1·
        1 hour ago

        Stupid question, Do you know if there is a similar method for qt apps installed through flatpak? I could not get Kate to use my accent color and it’s been driving me crazy. Also, happy we finally have a standard for accent colors. Now if we could just have a standard for global menus, probably wishful thinking.

      • Pasta Dental@sh.itjust.works
        17·
        12 hours ago

        I love the flatpak Wayland portals and systemd desktop stack. It allows Linux to finally have some sort of standard that everyone agrees on. This is what has been holding Linux back for so many years, it’s basically impossible to build a Linux app that will work for everyone because of this. Now we have a single dedicated system APIs that is available basically everywhere

          • Pasta Dental@sh.itjust.works
            3·
            4 hours ago

            There was always a need for a specific system dependency like for the file picker. There was no universal API that uses a system provided way to have a file picker. It had to be hacked together by adding dependencies to the app and everything that comes with this

        • D_Air1
          1·
          8 hours ago

          Well yes, but not really as not all desktops agree on and implement various wayland protocols and other features like the system tray, server side decorations, etc, etc. Quite a number of apps don’t work everywhere or appear broken depending on their environment. I’ve seen it happen live in a couple of youtube videos. People trying linux and having a problem that only exists on the desktop environment they were using.

          But I agree with the sentiment. Better than before.

          • Pasta Dental@sh.itjust.works
            4·
            8 hours ago

            the good thing is that virtually everyone uses GNOME and KDE, so the small issues are mostly encountered by more advanced users with custom setups. The main point is that app developers can now develop apps that will work anywhere that implements the required features, and if it doesnt, then too bad, show an error message. Its the same kind of problem with, for example, webcams. The user may or may not have a webcam connected, in which case you display an error popup with a clear message that it does not work because the feature is not implemented. They could go into fallbacks but those are usually platform/desktop specific (which goes against the point of building using the standard stack)

  • TimeSquirrel@kbin.melroy.org
    31·
    12 hours ago

    Now if they can fix the bug where once in a while I click to a tab and it doesn’t switch to it unless I minimize and maximize again, and needing a restart of the browser to get rid of that behavior…