When ESR 153.1 come out?

[anonymoustly]

When ESR 153.1 come out?

[krystian3w]

Preferably no earlier than two weeks before 18 August (so as not to have to guess what changes are already planned for version 153.2 on 15 September).

This calculation does not include the time taken for local compilation or the time taken to check whether 153 requires further patches (when those from Nightly 153 are not sufficient).

I can’t say whether the repository’s author will also discontinue the 153 ESR branch, meaning we’ll have to migrate to R3dfox ESR or use the fast/rapid releases every month.

[thinkpad4]

@e3kskoy7wqk has been working on his Chrome for Win7 repository for the last month or so, I guess getting that to a good stable state. Then he will be back here.

[JodyThornton]

@krystian3w writes ... I can’t say whether the repository’s author will also discontinue the 153 ESR branch, meaning we’ll have to migrate to R3dfox ESR or use the fast/rapis releases every month.

A lot of folks are saying this, but doesn't r3dFox ESR descend from e3k's releases? I'm surprised that compiling ESR versions is more difficult than release/nightly versions.

[bw134polska]

I'm afraid Firefox for Windows 7 is discontinued due to titlebar bug starting 150/151.

[krystian3w]

@bw134polska said: #170 (comment)

I'm afraid Firefox for Windows 7 is discontinued due to titlebar bug starting 150/151.

In 150 is not problem. in 151+ is a fix: #171

[JodyThornton]

Seems like the r3dFox crew figured the titlebar issue out, at least for Firefox v152.
Eclipse-Community/r3dfox#177

[krystian3w]

In that fork yes, in this one you can see they is waiting for the end of Chromium (for XP up) problems (optionally, the end of university exams to complete the semester/year/entire degre, where the chromium code may need to be developed for passing exam?) - #171 (doesn't appear to be merged in public files).

[thinkpad4]

@e3kskoy7wqk Hope you are doing ok. Haven't seen you around here in a while.

[e3kskoy7wqk]

I am currently doing a rework, so this repository will no longer be updated.

I am now working on version 91.0a1, which can run on Windows XP SP3 as the minimum requirement. @the-r3dacted and @mjd7989 are also involved in some way.

https://github.com/e3kskoy7wqk/Firefox-for-windows-7/releases/download/old/firefox-91.0a1.en-US.win32.installer.exe
https://github.com/e3kskoy7wqk/Firefox-for-windows-7/releases/download/old/firefox-91.0a1.en-US.win64.installer.exe

[thinkpad4]

@e3kskoy7wqk So will you make a Firefox for-windows-7-REWORK repository like you did for Chromium?

[e3kskoy7wqk]

@e3kskoy7wqk So will you make a Firefox for-windows-7-REWORK repository like you did for Chromium?

Yes, that's probably the case.

[Feodor2]

This is very interesting, so have you made webrender for winxp already? This is great if.
I shall take and check. 91 fine to chose, I can quickly make path to 105, I am to compare for speed and memory.
For mypal I try do less as possible memory and higher speed, especially for SSE only.
Today it almost in pair with 102 and 105 greatly, but significant faster and less memory consumption then originals.

[greyrat116]

Webrender (Software) can be made much faster in new versions of Firefox 102+

gfx.webrender.unaccelerated-widget.force - true
To speed up widgets you need DirectX10+. If DirectX9, it is “accelerated” by software and slows down the browser.

gfx.webrender.force-angle - false
Just like with widgets, DirectX10+ is required. If DirectX9, then it is “accelerated” by software and greatly slows down the browser.

The GPU process uses DirectX 9, but only works with Windows 7 (tested in MyPal 68; Windows XP and Vista SP1 use slow software implementation).
If you fix the GPU process, this will replace hardware acceleration in new versions of Firefox in which only Webrender (Software) is possible.

In Firefox 115+, Webrender (Software) uses DirectX 9 to partially accelerate the browser; in Linux OpenGL 2.0, acceleration must be enabled by setting layers.acceleration.force-enabled

OMTP is disabled (layers.omtp.enabled) in Firefox 91, and it doesn't work as expected in MyPal (layers.omtp.paint-workers). This feature will significantly improve the performance of browsers if it is fixed.

[JodyThornton]

So just to be clear @e3kskoy7wqk, are you halting development on Firefox for Windows 7? Including ESR development?

[Feodor2]

layers.omtp.enabled unnecessary on webrender, actually all layers not needed anymore.

But about:support is broken, how to check if webrender working then?