Eclipse Community

Duke wrote: *

27 Jul 2026, 12:58

Since you can add config keys through config.cfg then you don't need to hardcode them anymore.
So the advanced user can delete / edit the ones he wants and it might be easier and faster for you to add / edit / remove some keys

Ok, but then each update will replace config.cfg, unless you manually skip it, in which case you'll miss later changes that come from Librewolf.

Duke wrote: *

28 Jul 2026, 03:57

Because %OS_SLICE% returns Windows 7 or 8 which is not coherent with any version > 115. This may cause problems, check this:
https://board.eclipse.cx/viewtopic.php?p=9148#p9148

I've been thinking about removing that code because it adds complexity and requires reverting optimizations done to the browser code all for dynamic runtime OS spoofing. I should just fake 10 for those picky sites.

The-10-Pen wrote: *

28 Jul 2026, 05:03

Duke wrote: *

28 Jul 2026, 03:57

Because I have an account on some of these sites for years, and I don't want my user agent to appear with the F word in it.
Because %OS_SLICE% returns Windows 7 or 8 which is not coherent with any version > 115. This may cause problems, check this:
https://board.eclipse.cx/viewtopic.php?p=9148#p9148
Because I see no reason why I should be forced to use these keys. Actually it's a PITA to have to edit these user agents, one by one, each time a new version of R3dfox is released.

Totally agreed!
I was not familiar with the referenced "keys", but Holy Shit, Batman!
UA's with the F word is SO D@MN **CHILDISH**, thanks for the heads-up that SH!T like that is being hardcoded !!!

lol you should see the GitHub issue lol

the_r3dacted wrote: *

28 Jul 2026, 21:47

lol you should see the GitHub issue lol

Yeah, things like "trans-rights=human-rights". blah blah blah
There's "professional" and there's "childish", most of us know which is which when we see it.

The Notepad++ types of activism is never going to work for r3dfox.
At least I don't think it will, lol, what do I know.
I stopped updating mine BECAUSE of all the activism.
My old one works fine for everything I need it for.

You miss 100% of the shots you don't take.

About this issue report:
https://github.com/Eclipse-Community/r3dfox/issues/243

It happens because browser.settings-redesign.enabled is set to True, which is now the default in Firefox.

R3dfox v153.0.3 has been released:
https://github.com/Eclipse-Community/r3dfox/releases/tag/v153.0.3

Duke wrote: *

11 Aug 2026, 13:13

R3dfox v153.0.3 has been released

R3dfox v140.14.0 ESR is available:
https://github.com/Eclipse-Community/r3dfox/releases/tag/v140.14.0esr

About this issue report:
https://github.com/Eclipse-Community/r3dfox/issues/259

I'm quite sure the culprit is general.useragent.override.discord.com because:
You should NOT use F*ckAnubis in the user agent chain,
You should NOT use %OS_SLICE% in the user agent chain because Firefox > v115 is not supposed to run on Windows 7 & 8,
Some sites don't like older versions of browsers, so only the current version and maybe the version before are supported.

So the issue reporter should set this key value to "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:154.0) Gecko/20100101 Firefox/154.0" without quotes.
I think I already said it but we should not be forced to use these bypass Anubis user agents.

Duke wrote: *

27 Aug 2026, 15:13

About this issue report:
https://github.com/Eclipse-Community/r3dfox/issues/259

I'm quite sure the culprit is general.useragent.override.discord.com

I won't rule out the user agent as being a piece of the puzzle, however the underlying issue behind not being able to use cam/mic on Discord (and similar services) appears to be a deeper one :

https://github.com/Eclipse-Community/r3dfox/issues/257#issuecomment-5441473923

https://github.com/Eclipse-Community/r3dfox/issues/259#issuecomment-5441120246

Also, two facts:

a) Discord use CloudFlare as anti-bot protection, NOT Anubis
b) In (old) r3dfox-140.0.4, built with WebRTC enabled, the default discord SSUAO is:

Mozilla/5.0 (%OS_SLICE%; rv:109.0) Gecko/20100101 Firefox/115.0

however the browser has no issue accessing:

https://discord.com/invite/ecx

GoodConscience wrote: *

27 Aug 2026, 17:19

In (old) r3dfox-140.0.4, built with WebRTC enabled, the default discord SSUAO is:
Mozilla/5.0 (%OS_SLICE%; rv:109.0) Gecko/20100101 Firefox/115.0
however the browser has no issue accessing:
https://discord.com/invite/ecx

Yes, R3dfox v153.0.3 fails this WebRTC test:
https://browserleaks.com/webrtc



While it works with R3dfox v140.14 ESR.


Also reported here:
https://github.com/Eclipse-Community/r3dfox/issues/257#issuecomment-5441473923

Wow, I could finally log in after more than one week of a non working forum

Anyway, if R3dfox v155 is taking some time to be built maybe we could have meanwhile a R3dfox v140.15 ESR ?

Hello @all,

the 140.14.0 ESR works perfectly, thank you for the good work!

Unfortunately, things are different with the 150.x versions.

When the menu is turned on and you hover over the bookmarks works, all folders will be marked.

If I start a video conference, the message appears:
"WebRTC is not available in your browser
It looks like your browser does not support WebRTC.
Please enable it or try another browser."

Note:
media.peerconnection.enabled is true

Is there a way to change this?

Archer wrote: *

06 Sep 2026, 10:07

things are different with the 150.x versions.

If I start a video conference, the message appears:
"WebRTC is not available in your browser
It looks like your browser does not support WebRTC.
Please enable it or try another browser."

Note:
media.peerconnection.enabled is true

Is there a way to change this?

I'm afraid not at the moment. Read this post and mine after:
https://board.eclipse.cx/viewtopic.php?p=9530#p9530

For now for WebRTC use R3dfox v140.14 ESR which is better than an older version of R3dfox non ESR.

About this issue report:
https://github.com/Eclipse-Community/r3dfox/issues/262

The game is working fine for me with R3dfox v153.0.3 and R3dfox v140.14 ESR if I allow WebGL context.

Duke wrote: *

06 Sep 2026, 10:25

For now for WebRTC use R3dfox v140.14 ESR which is better than an older version of R3dfox non ESR.

... We're all very well aware that you tend to focus more on security patches rather than overall web compatibility ...

The fx140esr branch will become EoL at the end of the current month (actually on 29 Sep 2026), with the next ESR branch being shifted to v153(esr); many of the "trendy" services requiring WebRTC to function will start to move away from supporting 140esr and will move on to 153esr (again, for "security" reasons ), so one, in the coming month(s), may have better chances, from a webcompat standpoint, of having their "video call site" work better in r3dfox-v152.0.4-hotfix, currently the last "recent" (on the release-channel) version compiled with WebRTC support; assuming that the r3dfox author doesn't re-enable WebRTC at buildtime in the next v154.0.x build (or later) ; the v152.0.4-2 (non-working) release notes did mention:

Quote:

Disabled WebRTC because it didn't work anyways and faster to compile without.

but it appears that detail went unnoticed by the majority of users ...

GoodConscience wrote: *

06 Sep 2026, 13:35

you tend to focus more on security patches rather than overall web compatibility ...

many of the "trendy" services requiring WebRTC to function will start to move away from supporting 140esr and will move on to 153esr

What makes you thinking that WebRTC won't work anymore in v140 ESR ?
Any source about that ?

GoodConscience wrote: *

06 Sep 2026, 13:35

Quote:

Disabled WebRTC because it didn't work anyways and faster to compile without.

but it appears that detail went unnoticed by the majority of users ...

Yes, I admit I missed this information.

Duke wrote: *

06 Sep 2026, 16:11

What makes you thinking that WebRTC won't work anymore in v140 ESR ?

... I didn't say that the WebRTC feature itself might quit working in r3dfox-140.14.0esr in the coming weeks (although the feature does get security and performance updates by upstream, i.e. Mozilla), I hinted that the web services/sites (e.g. Discord, Zoom, etc.) requiring it will start blocking fx-140esr-based browsers, due to 140esr no longer being supported by Mozilla, as being insecure, etc. (one might get the error message: Your browser is no longer supported by "us"; update to the latest version of Firefox), at first via a user-agent filter and later by implementing JS+CSS code NOT supported by fx140esr and earlier; this is what they usually do ...