Looks the same to meI was right about the font change.
v134.0.2:
![]()
v135.0:
![]()

EDIT: Oh no wait, it looks a bit softer the bottom one!
Last edited:
Looks the same to meI was right about the font change.
v134.0.2:
![]()
v135.0:
![]()
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.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.
Yeah it looks subtle in those images, but save them and flick between them and the difference is night and day to me.Looks the same to me
EDIT: Oh no wait, it looks a bit softer the bottom one!
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.![]()
Just compared it with Vivaldi/Edge, it seems more similar to the way Chromium renders fonts now. Shame as I preferred the sharper look on FF.I was right about the font change.
v134.0.2:
![]()
v135.0:
![]()
I've still got the Report Broken Site option in my menu, v135.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.![]()
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.
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.
I am with BT.
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.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.
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%.
I wonder if they have similar plans for Windows users? While Firefox seems reasonably nimble on Windows these days, any speed boost is always welcome.