Switch Firefox from Flatpak to RPM with win95 retro theme#94
Draft
ledif wants to merge 7 commits into
Draft
Conversation
- Replace org.mozilla.firefox Flatpak with firefox RPM - Add 25-firefox-theme.sh: builds win95-themes CSS at image build time, installs fx-autoconfig to /usr/lib64/firefox/, stages theme files to /usr/share/winblues/firefox-theme/, sets system-wide Firefox prefs - Add run_after_04-firefox-theme.sh: chezmoi first-login script that wires up the chrome/ directory in the user's default Firefox profile - Update panel launcher from Pale Moon to native Firefox RPM WIN95_SHA=d1d459c78939 (v2.3.0), FXAC_SHA=54f88294ea70
…ng path Firefox copies browser/defaults/profile/chrome/ into every new profile automatically on first launch, so no chezmoi profile-detection is needed for fresh installs. The chezmoi script is now upgrade-only: it copies chrome/ into any existing profiles that are missing it.
- Replace vendored fx-autoconfig config.js with a custom version that copies chrome/ from browser/defaults/profile/chrome/ on first launch if chrome/utils/ is missing. Firefox does not copy defaults/profile/ to new profiles automatically, so the loader must do it. - Fix chezmoi script to check ~/.config/mozilla/firefox/ (XDG) first, falling back to ~/.mozilla/firefox/ for legacy systems.
Three bugs prevented the theme from rendering correctly: - CSS/colors/ dir was not created; win95.colors pref was not set, so all three @import color conditionals in firefox_global.uc.css evaluated false and no --color-* variables were defined, making the entire theme invisible - browser.tabs.inTitlebar was not set to 0, so Firefox used CSD instead of letting xfwm4/Chicago95 draw the Win95-style WM title bar - win95.navbar-button-labels was not enabled; add it as the system default for authentic Win95 IE-style labeled toolbar buttons
…displays Win95's original 8pt (11px at 96dpi) is uncomfortably small on modern monitors. Override --text-ui-size via a cascade-order append to userChrome.css so all tab/toolbar/URL text renders at 14px.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
System prefs set
Pinned versions
Testing
To test without waiting for CI, rebase to the PR image tag once the CI build completes:
```
rpm-ostree rebase ostree-image-signed:docker://ghcr.io/winblues/blue95:pr-94-43
```
Or test the theme wiring live on an unlocked system by running `25-firefox-theme.sh` directly and then triggering the chezmoi script.
Maintenance note
The win95-themes CSS targets Firefox internal element IDs which can break on Firefox updates. Firefox is not pinned — it updates freely via the base image. When the theme breaks after a Firefox update, bump `WIN95_SHA` in `25-firefox-theme.sh` to the latest win95-themes release and rebuild.