firefox: support Glide derivative

[zzzealed]

Hello and thanks for your work on Stylix :)

I added Glide to the Firefox (and derivatives)-module, since Glide now has a Home Manager-module made with mkFirefoxModule. This means it should be compatible with the same options as the other derivatives.

I tested this myself and can confirm that the options looks to be working.

I hope I added everything correctly, as this is my first time making a contribution. Please do not hesitate to leave feedback or request changes.

---

• I certify that I have the right to submit this contribution under the MIT license
• Commit messages adhere to Stylix commit conventions
• Theming changes adhere to the Stylix style guide
• Changes have been tested locally
• Changes have been tested in testbeds
• Each commit in this PR is suitable for backport to the current stable branch

[trueNAHO]

CI is currently failing because lib.maintainers.zzzealed and glide-browser are undefined. If these are recent upstream additions, this PR requires #2180 to be merged first.

• Each commit in this PR is suitable for backport to the current stable branch

Are the necessary upstream patches available in our release-25.11 branch?

I hope I added everything correctly, as this is my first time making a contribution.

LGTM, except for one nitpick. I will also test this PR in a testbed once CI is working again.

[zzzealed]

CI is currently failing because lib.maintainers.zzzealed and glide-browser are undefined. If these are recent upstream additions, this PR requires #2180 to be merged first.

Yeah so I removed myself as maintainer since I'm not in maintainer-list.nix. I hope this is fine.
For glide-browser being undefined, I think this happens because Glide isn't actually merged to nixpkgs yet. I use their flake's Home Manager module.
I don't know if Stylix has any policy on non-nixpkgs (yet) projects, like Glide. Please let me know if that's the case.

Are the necessary upstream patches available in our release-25.11 branch?

Yes it look's to me like release-25.11 has the sufficient patches.

[0xda157]

CI failures seem to be unrelated to this PR's changes, could you force push to trigger a re-run? also ideally a testbed would be added before merging.

[zzzealed]

also ideally a testbed would be added before merging.

Sure I can do that. As I said Glide isn't in Nixpkgs but I could just add Glide's input in flake.nix and copy the modules/firefox/testbeds/firefox.nix. Then lastly import and modify modules/firefox/testbeds/firefox-color.nix and modules/firefox/testbeds/firefox-gnome-theme.nix.

Does this approach make sense?

[trueNAHO]

I removed myself as maintainer since I'm not in maintainer-list.nix. I hope this is fine.

It would be highly appreciated to add yourself as a maintainer so you are notified about potential Glide issues. The process is already documented:

stylix/doc/src/modules.md

Lines 225 to 251 in 8ed48a4

	### Maintainers
	New modules must have at least one maintainer.
	If you are not already listed in the Nixpkgs `/maintainers/maintainer-list.nix`
	maintainer list, add yourself to `/stylix/maintainers.nix`.
	Add yourself as a maintainer in one of the following ways, depending on the
	number of maintainers:
	- ```nix
	{ lib, ... }:
	{
	maintainers = [ lib.maintainers.danth ];
	}
	```
	- ```nix
	{ lib, ... }:
	{
	maintainers = with lib.maintainers; [
	danth
	da157
	noahbiewesch
	];
	}
	```

Otherwise, inspect commits touching /stylix/maintainers.nix for further inspiration.

I don't know if Stylix has any policy on non-nixpkgs (yet) projects, like Glide. Please let me know if that's the case.

[...]

Glide isn't in Nixpkgs but I could just add Glide's input in flake.nix

Yes, this is how we handle external module integration, except that we do not publicly expose these test inputs by adding them to the internal /flake/dev/flake.nix. See commit aa0272b ("dank-material-shell: init (#2177)") as an example.

and copy the modules/firefox/testbeds/firefox.nix. Then lastly import and modify modules/firefox/testbeds/firefox-color.nix and modules/firefox/testbeds/firefox-gnome-theme.nix.

Yes, adding a testbed for this external module would be highly appreciated. I suppose adding a single /modules/firefox/testbeds/glide.nix testbed suffices.

[zzzealed]

Hello :)
I made the changes as suggested. Hopefully this is what you had in mind.

I also tried cleaning up the commits a bit.

Let me know if there are more changes needed.

[trueNAHO]

Try resolving the CI failures and verify the theme working inside the nix run .#testbed:glide:{dark,light} testbeds.

[zzzealed]

nix run .#testbed:glide-browser:light and nix run .#testbed:glide-browser:dark looks correct now.

[trueNAHO]

Try resolving the CI failures

Maybe the following resolves the aarch64-linux failures:

diff --git a/modules/firefox/each-config.nix b/modules/firefox/each-config.nix
index 846eb20d..11fb227a 100644
--- a/modules/firefox/each-config.nix
+++ b/modules/firefox/each-config.nix
@@ -9,6 +9,7 @@
   lib,
   pkgs,
   config,
+  options,
   ...
 }:
 mkTarget {
@@ -26,7 +27,7 @@ mkTarget {
     firefoxGnomeTheme.enable = lib.mkEnableOption "[Firefox GNOME theme](https://github.com/rafaelmardojai/firefox-gnome-theme) on ${humanName}";
   };

-  config = [
+  config = lib.optionals (name == "glide-browser" -> options.programs ? ${name}) [
     (
       { cfg }:
       {