Some "Something went wrong" on some websites, with default install 132.0 (64b)

[Shadebzh]

On some websites, I get a "Something went wrong"), for example with https://deliveroo.com
don't know why, with default install, new profil, no plugin or added modules.

Works with official Firefox ESR (and chromium like browsers)

Thank you.

[informatorius]

I see the same with r3dfox 128.4.0esr (64-Bit) on Windows 7 64bit latest patches

[K4sum1]

Weird. I'm not sure why this issue happens. I figured it didn't like the useragent, but it still happens with faked normal Firefox useragent.

[J4CKED]

Similar problem. Polish auction site https://allegro.pl/ does not work (error: The connection has timed out) in version 132, Plasmafox.
In version 129, the site works.

[K4sum1]

Interesting, if you can find a version where a given site works and the first version it's broken in, I might be able to look into it.

[J4CKED]

I don't know what's going on anymore. Now the allegro.pl website is working in both browser versions.

But the website https://deliveroo.com does not work in version 132.0 x64 portable.
It works in version 129.0.2 x64 portable.

[K4sum1]

Now what about 130, 131, and 133?

[J4CKED]

https://deliveroo.com/ = 130, 131, 132, 133 not working (all x64 portable)

[K4sum1]

I'll have to check with stock Firefox releases when I get to testing them. If it's an upstream issue, it's not really something I can fix.

[K4sum1]

Well, I fired up my 8.1 VM and I had Firefox 131 (modded) and r3dfox 131 already there, so I figured I'd try now. It works in Firefox and not r3dfox. Maybe it could be related to one of the privacy tweaks I did, not sure.

[K4sum1]

Disabling beacon.enabled breaks the site.

I remember being a bit hesitant to disable it since it is a web feature, however I was convinced to do it for 130. I guess I was correct in being hesitant. It'll be enabled for next release.