Eclipse Community

DoNotThrowOldPCsAway wrote: *

02 Aug 2025, 19:29

I love the ability to unload tabs!

For those not in the know:

https://support.mozilla.org/kb/unload-tabs-reduce-memory-usage-firefox

But I've been doin' the exact same thing many versions prior to r3dfox-140.0.4 via an extension:

https://addons.mozilla.org/firefox/addon/auto-tab-discard/

With the unload tabs feature, this should make for a really cool ESR release, but at least before all of the AI stuff inundates us.

K4sum1 wrote: *

25 Jul 2025, 15:26

So current 140 and 141 will likely just be a basic upgrade with no other major changes.

Hope it will be the same for v142 because we never saw R3dfox v141 (yet ?)

Yeah, I just haven't been feeling it. I'd have to migrate to another repo because Mozilla made a new Firefox repo on GitHub. I don't know when I will get around to it.

K4sum1 wrote: *

19 Aug 2025, 22:46

Yeah, I just haven't been feeling it. I'd have to migrate to another repo because Mozilla made a new Firefox repo on GitHub. I don't know when I will get around to it.

Is that the same for ESR K4Sum1? No pressure; I'm just curious.

JodyThornton wrote: *

19 Aug 2025, 23:58

K4sum1 wrote: *

19 Aug 2025, 22:46

Yeah, I just haven't been feeling it. I'd have to migrate to another repo because Mozilla made a new Firefox repo on GitHub. I don't know when I will get around to it.

Is that the same for ESR K4Sum1?

If you're referring to the change of repos, I'm afraid it is:

https://github.com/mozilla-firefox/firefox/tree/esr140

(previously hosted on https://hg-edge.mozilla.org/releases/mozilla-esr140/ ?)

https://www.heise.de/en/news/Mozilla-uses-Microsoft-GitHub-as-the-official-home-for-Firefox-source-code-10384645.html

https://devclass.com/2025/05/14/mozilla-quietly-makes-microsofts-github-the-authoritative-home-for-firefox-code/

GitHub, of course, is owned by Microsoft ...

Probably related, several other Firefox-specific resources also recently changed URLs, e.g.

https://www.mozilla.org/en-US/firefox/140.2.0/releasenotes/ =>

https://www.firefox.com/en-US/firefox/140.2.0/releasenotes/

Hope all is well; k4.

Greetings.
The new repo of r3dfox is:
https://github.com/Eclipse-Community/r3dfox-new

K4sum1 wrote: *

19 Aug 2025, 22:46

Yeah, I just haven't been feeling it.
I don't know when I will get around to it.

Just do things. Believe me it's the best way for feeling better.
Doing round circles just leads you to do more round circles and again etc etc... Vicious circle.

PantelicGR wrote: *

25 Aug 2025, 16:26

Greetings.
The new repo of r3dfox is:
https://github.com/Eclipse-Community/r3dfox-new

No downloadable assets though yet, is that correct, or am I missing it? I can totally ignore the old page, correct?

JodyThornton wrote: *

25 Aug 2025, 23:45

No downloadable assets though yet, is that correct, or am I missing it?

Yes, it's just a new repo with no downloadable releases yet.

JodyThornton wrote: *

25 Aug 2025, 23:45

I can totally ignore the old page, correct?

I don't know about that. I'm following both new and old r3dfox repo just to be sure to notice the new changes and releases.

PantelicGR wrote: *

26 Aug 2025, 17:36

JodyThornton wrote: *

25 Aug 2025, 23:45

I can totally ignore the old page, correct?

I don't know about that. I'm following both new and old r3dfox repo just to be sure to notice the new changes and releases.

Same here. Trying to be patient

PantelicGR wrote: *

26 Aug 2025, 17:36

JodyThornton wrote: *

25 Aug 2025, 23:45

I can totally ignore the old page, correct?

I don't know about that. I'm following both new and old r3dfox repo just to be sure to notice the new changes and releases.

Well that's interesting. The old page must be gone, because the new page now just switches to the old URL.

The only thing is, all of the open issues will now be gone ... lol

JodyThornton wrote: *

27 Aug 2025, 10:32

Well that's interesting. The old page must be gone, because the new page now just switches to the old URL.
The only thing is, all of the open issues will now be gone ... lol

The new repo's URL has changed to:
https://github.com/Eclipse-Community/r3dfox

And the old repo's URL has changed to:
https://github.com/Eclipse-Community/r3dfox-old

So, nothing is lost for now.

JodyThornton wrote: *

27 Aug 2025, 10:32

The old page must be gone, because the new page now just switches to the old URL.

It was announced and explained by the maintainer some 5 days ago, in a low-visibility GitHub comment :

https://github.com/Eclipse-Community/r3dfox-old/issues/317#issuecomment-3215950463

JodyThornton wrote: *

27 Aug 2025, 10:32

The only thing is, all of the open issues will now be gone...

Yes, if the r3dfox-old repo is to be archived, all open/closed issues in its tracker will become inactive, with no way to comment/edit anymore ... I agree with you that this shouldn't happen...

The ideal solution would be for @K4sum1 to extract the redfox-old repo issue tracker as it currently stands prior to archiving the repo and then insert/merge it with the (new) redfox repo issue tracker; that way, the old tracker will be preserved in the newly created repo...
GitHub provides semi-automated ways for issue tracker extraction and re-introduction to a new repo (by the same owner), but don't ask me about those details ...

https://stackoverflow.com/questions/9720718/how-do-i-move-an-issue-on-github-to-another-repo

https://docs.github.com/en/issues/tracking-your-work-with-issues/administering-issues/transferring-an-issue-to-another-repository

https://github.com/orgs/community/discussions/9695

I'm only transferring critical or still relevant issues to the new repo. I'm leaving a lot of the older issues in place in the old repo.

I'm probably not going to fully archive the old repo for a while. I still have for example half done ESR 115 FTP support in the old repo and I don't feel like making a new branch for it and converting everything yet.

New repo is going to be used for new releases from now on.

K4sum1 wrote: *

28 Aug 2025, 13:09

New repo is going to be used for new releases from now on.

R3dfox v141.0.3 is out:
https://github.com/Eclipse-Community/r3dfox/releases/tag/v141.0.3

And also R3dfox v140.2.0 ESR:
https://github.com/Eclipse-Community/r3dfox/releases/tag/v140.2.0

Oh Yaaaaa! (Cue the Kool Aid Guy!)
Thanks so much K4Sum1

I can confirm this bug with R3dfox 141.0.3:
https://github.com/Eclipse-Community/r3dfox/issues/37

about:confignew is working fine though.

Duke wrote: *

29 Aug 2025, 14:55

I can confirm this bug with R3dfox 141.0.3:
https://github.com/Eclipse-Community/r3dfox/issues/37

about:confignew is working fine though.

What exactly is about:confignew? (as opposed to about:config, I mean)

JodyThornton wrote: *

29 Aug 2025, 15:07

What exactly is about:confignew? (as opposed to about:config, I mean)

In R3dfox about:config is like the old legacy about:config of Firefox (before v69 I think, maybe v52) showing status and type while about:confignew is the current 'modern' about:config of Firefox.

Duke wrote: *

29 Aug 2025, 16:33

In R3dfox about:config is like the old legacy about:config of Firefox (before v69 I think, maybe v52) showing status and type while about:confignew is the current 'modern' about:config of Firefox.

Does it matter which one I use to modify prefs?

JodyThornton wrote: *

29 Aug 2025, 17:31

Does it matter which one I use to modify prefs?

Not at all. You can check it yourself by comparing the values in each layout.

The taskbar bug is back in v141.0.3
https://board.eclipse.cx/viewtopic.php?p=6857#p6857
https://board.eclipse.cx/viewtopic.php?p=6901#p6901

It's working fine in v140.0.4.

https://github.com/Eclipse-Community/r3dfox/issues/38 wrote:

I also disabled the screenshot tool because why does the browser need a screenshot tool? You can just screenshot the browser with an external program or the classic print screen key.

The print screen key only captures the visible part, not the entire page.
The built-in tool allows to capture the whole page and also to easily define the part of the page to be saved with some kind of automated selection. It's easy to use and a really handful tool.

Why should I have to use an external tool while the built-in one has everything we need ?
Not to mention all of the tools I've tried have problems to capture the entire page on some sites.
Please restore back this useful feature.

EDIT: I've found a workaround.
First copy the screenshots@mozilla.org.xpi extension from an older version of R3dfox (last one to have it is v137.0.2) or from Firefox to the \r3dfox\core\browser\features folder. Create this destination folder if it doesn't exist yet.
Then in about:config set screenshots.browser.component.enabled to true.
You may need to restart R3dfox.

Duke wrote: *

29 Aug 2025, 14:55

I can confirm this bug with R3dfox 141.0.3:
https://github.com/Eclipse-Community/r3dfox/issues/37

about:confignew is working fine though.

Fixed in the hotfix version:
https://github.com/Eclipse-Community/r3dfox/releases/tag/v141.0.3-hotfix

Duke wrote: *

30 Aug 2025, 09:04

EDIT: I've found a workaround.
First copy the screenshots@mozilla.org.xpi extension from an older version of R3dfox (last one to have it is v137.0.2) or from Firefox to the \r3dfox\core\browser\features folder. Create this destination folder if it doesn't exist yet.
Then in about:config set screenshots.browser.component.enabled to true.
You may need to restart R3dfox.

Greetings and thanks ; I'm still on r3dfox-v140.0.4-win32 portable (on Vista SP2 32-bit), where the native screenshot tool still works fine ; however, it doesn't have a ".\browser\features" directory with the screenshots@mozilla.org.xpi file inside it; so, how is it that v140.0.4 has a working screenshot tool?
Are you sure that just toggling screenshots.browser.component.enabled to true (and restarting the browser) isn't enough in the case of v141.0.x ?

GoodConscience wrote: *

30 Aug 2025, 21:03

Are you sure that just toggling screenshots.browser.component.enabled to true (and restarting the browser) isn't enough in the case of v141.0.x ?

Looks like you're right, the screenshot feature seems to be now built-in into the browser core and enabling screenshots.browser.component.enabled should be enough.

Duke wrote: *

29 Aug 2025, 22:16

The taskbar bug is back in v141.0.3
https://board.eclipse.cx/viewtopic.php?p=6857#p6857
https://board.eclipse.cx/viewtopic.php?p=6901#p6901

It's working fine in v140.0.4.

Annoyance is still there in v142.0.1

Duke wrote: *

05 Sep 2025, 23:39

Duke wrote: *

29 Aug 2025, 22:16

The taskbar bug is back in v141.0.3
https://board.eclipse.cx/viewtopic.php?p=6857#p6857
https://board.eclipse.cx/viewtopic.php?p=6901#p6901

It's working fine in v140.0.4.

Annoyance is still there in v142.0.1

https://github.com/e3kskoy7wqk/Firefox-for-windows-7/issues/78