Why you SHOULD be using Firefox

I was right about the font change.

v134.0.2:
1.png


v135.0:
2.png
Looks the same to me :D

EDIT: Oh no wait, it looks a bit softer the bottom one!
 
Last edited:
Yeah I noticed straight away the font has changed - it seems to depend on screen - on my older RGB TN and IPS types it is much clearer than before, on newer display technologies especially those with BGR layout it is less clear than before though not a huge change.
I have an older TN monitor and find the newer font less comfortable to read. To be honest, I thought I had a dodgy cable at first. :D

Looks the same to me :D

EDIT: Oh no wait, it looks a bit softer the bottom one!
Yeah it looks subtle in those images, but save them and flick between them and the difference is night and day to me.

Annoying, to the say the least.
 
Last edited:
I have an older TN monitor and find the newer font less comfortable to read. To be honest, I thought I had a dodgy cable at first. :D

Was going to add, but trying to keep the post from rambling, it isn't consistent - some displays regardless of type seem to work with the font change better or worse.
 
Last edited:
Well this really annoys me....

Mozilla removed the ability from the browser to send feedback to them about websites not working.

For months now the UK river website has been running super slow. I put it down to them.

However I have just realized the issue isn’t them but Firefox!

It runs super slow, loads incompletely and I have to refresh to get it to load.

And I cant even send them feedback that the website is not working properly in Firefox!
I've still got the Report Broken Site option in my menu, v135. :confused:
 
If you can’t see the report site option, it means you have turned off data collection and usage option in Firefox previously.
The new site reporter tool requires collecting data and sending it to Mozilla developer team, so if the data collection option is disabled, the new site reporter tool option will not be available.
 
Last edited:
Ok so I just tried the digital river on a other computer (no shared profile etc) and it does the same thing. Hanging connection then partial load.

I am using Clouflare DNS... I might try Google.
 
Last edited:
Bit of a weird one - I had similar problems years ago, though I can't remember details now, on BT where certain HTTPS connections were failing to load properly and required refreshing the page, often affecting Firefox the most.
 
So I have switched to Google DNS and it is now much better.... not perfect there are still some parts of the digital river that hang or take a while but it is much much improved compared to using Cloudflare for DNS.

---

Initially it seemed better but now it is going back to hanging.
 
Last edited:
I am with BT.

Maybe it is still an ongoing thing with BT, though technically my 4G EE connection is now BT. I only really use the BT FTTC here for gaming due to having low latency as the bandwidth is low, and 4G EE or another provider wireless for general internet use due to the better bandwidth.
 
Do people have DNS over HTTPS enabled in the browser?

If this was a DNS issue it wouldn’t be working fine in Edge.

Only FF is having problems.
I have DNS over HTTPS enabled at max protection. I use Cloudfare and my ISP is Virgin Media. Amazon.co.uk (yes you are allowed to mention Amazon, just don't link to products on their site that OcUK sell) works fine for me, but I'll keep an eye on it, as I need to use Amazon to hunt for some bits soon.
 
I have it enabled too, set to increased and have Cloudflare set. ISP is Community Fibre.

I guess another thing you can try is disable IPv6 and see if that makes any difference? Only other thing I can think of, maybe FF is not properly falling back to IPv4 if IPv6 isn't working.
 

Mozilla engineer Alexandre Lissy presented at the FOSDEM 2025 conference earlier this month on Mozilla's ForkServer for Linux within Firefox for improving the multi-process handling within the web browser. This is part of the evolution of the multi-process Firefox handling as a process dedicated to fork() handling that is faster and lighter weight than the status quo.

Since last October nightly builds of Firefox on Linux have begun using ForkServer. It appears to be reliable and the most important aspect for end-users is the performance wins with base resident memory around 50% lower and the content process startup is reduced by around 35%.
 
Back
Top Bottom