r3dfox, a modern Firefox based web browser for Windows Vista, 7, and 8!

[vinifera]

new version is up ! <3

[vinifera]

new version is up

[Jody Thornton]

I'm hoping for an update to ESR 128.10, as there was a major security patch issued last month.  I think ESR 128.11 was next.  Crossing my fingers

 

[Mathwiz]

On Win 7, R3dfox is now my preferred replacement for M$ Edge. I had been using the latest Edge version for Win 7 (109), with a UAO to Chrome 125, but that's no longer good enough for some sites (e.g., discover.com).

I did find that Chase.com doesn't like the R3dfox slice in the user agent - or was it the OS slice, revealing Win 7, that it was objecting to? It kept telling me to "upgrade" my browser even though R3dfox is up to version 139! Well, either way, a straight FF 128 on Win 10 user agent satisfies both Chase and Discover, at least for now.

It's ridiculous how bloody finicky some Web sites - particularly financial ones - have become. Security I dig, but way too many folks equate "security" with "only using Chrome, Edge, or Firefox, and a version no older than a few months."

[K4sum1]

15 minutes ago, Mathwiz said:

I did find that Chase.com doesn't like the R3dfox slice in the user agent - or was it the OS slice, revealing Win 7, that it was objecting to? It kept telling me to "upgrade" my browser even though R3dfox is up to version 139! Well, either way, a straight FF 128 on Win 10 user agent satisfies both Chase and Discover, at least for now.

It's probably the r3dfox bit at the end, but idk. Try experimenting with general.useragent.override.chase.com and general.useragent.override.discover.com and I'll add what works best to the next release.

[Jody Thornton]

New ESR releases for 128.12 (including a hotfix) ... yay!

https://github.com/Eclipse-Community/r3dfox/releases/tag/v128.12.0rc-hotfix

[Jody Thornton]

Darn!  Seems the new release doesn't support tabs under the address bar (by using Zapp's Photon Theme).  Still works with ESR 128.10.  I wonder if something changed in core Firefox, but there are A LOT of different r3dFox options in Settings now.

 

Edit:  It appears that custom entries in about:config that are used by Zapp's Photon Theme are now ignored by ESR 128.12 rc

GoodConscience wrote: on the Eclipse Forum:  "This version of r3dfox isn't completely compatible with 128 ESR userChrome.css themes.
You will need to replace instances of "(-moz-bool-pref: " with "-moz-pref(" for the theme to work correctly

That did fix it.

 

Edited June 14 by Jody Thornton

[Mathwiz]

On 6/10/2025 at 11:00 PM, K4sum1 said:

It's probably the r3dfox bit at the end, but idk. Try experimenting with general.useragent.override.chase.com and general.useragent.override.discover.com and I'll add what works best to the next release.

Discover.com works with r3dfox as-is, so no SSUAO needed there. (Edge or Thorium users aren't so lucky; Discover seems to demand a quite recent Chromium engine. Supermium would probably do the trick but I haven't tried it.)

I see several sites with this SSUAO: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:128.0) Gecko/20100101 Firefox/128.0

This works with chase.com as well. So I guess it was the r3dfox bit that it didn't like after all. Win 7 doesn't seem to bother it.

[vinifera]

On 6/11/2025 at 6:00 AM, K4sum1 said:

It's probably the r3dfox bit at the end, but idk. Try experimenting with general.useragent.override.chase.com and general.useragent.override.discover.com and I'll add what works best to the next release.

i always up my number by 100
and fake it is Linux OS

don't get any complaints from web...
even protonmail falls for it

 

Edited June 15 by vinifera

[Jody Thornton]

I'm in no hurry @K4sum1, but I am curious.  Will r3dFox be moving into ESR 140 territory?  I posted on Eclipse, but I was just curious to know. 

 

[K4sum1]

r3dfox 140 will come soon

[Jody Thornton]

Great news - I received the notice on GitHub.

No rush.  I just wondered if it was going to be a thing.  Thanks K4Sum1

 

[vinifera]

On 7/25/2025 at 4:26 PM, K4sum1 said:

r3dfox 140 will come soon

 r3dfox specific changes on top of the previous v139.0.4-2 build:

No major changes worth noting.

then why update to it ?

[VistaLover]

One of the features of r3dfox I like the most  is the fact it allows for the installation of UNSIGNED Firefox extensions, despite itself being derived from the "Release Branch" of upstream Mozilla Firefox; in "stable" (and "beta") Firefox, the pref "xpinstall.signatures.required" defaults to "true" but even when toggled, it doesn't produce the desired effect: UNSIGNED extensions remain incompatible and won't install  (Mozilla's decision to protect the "masses" - this term is now used loosely, considering the declining Firefox userbase  - from shooting themselves in the foot ) ...

The way r3dfox achieves this is via two buildconfig flags (issued at build time): 

 --with-unsigned-addon-scopes=app,system --allow-addon-sideload

; additionally, in the resulting binaries, "xpinstall.signatures.required" defaults to "false"  ...

As in the case of ESR Firefox/r3dfox builds, the add-ons manager (AOM, about:addons) will let you know of installed unsigned extensions, if any, by displaying a coloured "warning" bar underneath each unsigned extension (taken from 128.12.0esr): 

Personally, I regard these "warning" bars as (slight) irritants, polluting my AOM's view, so, starting with r3dfox-115.13.0esr onwards, I have been systematically hiding them via custom userContent.css code: 

/* Remove "Recommendations" from AOM, https://www.reddit.com/r/firefox/comments/184nqq0/how_to_remove_recommendations_page_in_firefox/ */
@-moz-document url-prefix(about:addons) {
  .category[name="discover"] {
    display: none !important;
  }
  .addon-card-message[type="warning"] {
    display: none !important;
  }
}

Above code was working flawlessly up-to-and-including r3dfox-139.0.4-2 (Greek, "el", locale shown below): 

Enter r3dfox-140.0.4 , to which I updated yesterday; imagine my surprise+disappointment  when the AOM was loaded: 

Make no mistake; I did go through 140's Release Notes as hosted on GitHub, prior to installing, and, as another MSFN member noted, they stated: 

Quote

r3dfox specific changes on top of the previous v139.0.4-2 build:
No major changes worth noting.

IMHO though, any r3dfox-specific change likely to interfere with user customisation, however small, IS worth mentioning in Release Notes...

Luckily for me, I found my way to 140's source code in GitHub and immediately noticed what looked to be the culprit commit: 

https://github.com/Eclipse-Community/r3dfox/commit/c69c8d07e9e421ef8b3f3ea6b730f8b3a4443fa8

With respect to the browser author  , changing the "aboutAddons.ftl" file, part of the embedded en-US locale, isn't a smart thing to do, unless: 1) you restrict users exclusively to the embedded en-US locale, 2) you have the resources to produce yourself (i.e. translate from English-US) the rest of the locales; e.g., once one installs the Mozilla-provided 140.0.4_en-GB locale, the author changes are being reverted to what the Mozilla wording is: 

FWIW, the change in the "aboutaddons.js" file is what BROKE my custom CSS code above; sanity returned when the code was amended accordingly : 

/* Remove "Recommendations" from AOM, https://www.reddit.com/r/firefox/comments/184nqq0/how_to_remove_recommendations_page_in_firefox/ */
@-moz-document url-prefix(about:addons) {
  .category[name="discover"] {
    display: none !important;
  }
/* https://github.com/Eclipse-Community/r3dfox/commit/c69c8d07e9e421ef8b3f3ea6b730f8b3a4443fa8#diff-602c847d11b48c077836e06c7ee9e9e8450ad6a90d39211ba75530743c44fbb7 */
  .addon-card-message[type="info"] {
    display: none !important;
  }
}