The visibility of fonts to websites has been restricted to system fonts and language pack fonts in Enhanced Tracking Protection strict mode to mitigate font fingerprinting.
I’m happy to see this. It’s crazy how hard advertisers try to determine who I am when I’m actively attempting not to be shown their garbage and won’t buy it from their links. Browsers should be sending far fewer html headers, and restricting the listed fonts to a common list is a good step forward.
I keep waiting for better profile management. Not saying it needs to mirror chrome exactly, but feature wise it falls short (at least how I would like to use it).
They are completely isolates browser settings. Account, session, settings, hardening, history, everything.
To a certain extent you can do that with multi-account containers.
For instance, I can have Amazon always open in my “Shopping” tab to keep it separate from my “Social Networks” tab.
my list of cool features:
Gradually rolling out in Fx119, Firefox now allows you to edit PDFs by adding images and alt text, in addition to text and drawings.
If you’re migrating your data from Chrome, Firefox now offers the ability to import some of your extensions as well.
As part of Total Cookie Protection, Firefox now supports the partitioning of Blob URLs, this mitigates a potential tracking vector that third-party agents could use to track an individual.
The visibility of fonts to websites has been restricted to system fonts and language pack fonts in Enhanced Tracking Protection strict mode to mitigate font fingerprinting.
Encrypted Client Hello (ECH) is now available to Firefox users, delivering a more private browsing experience. ECH extends the encryption used in TLS connections to cover more of the handshake and better protect sensitive fields.
Firefox is now available in the Santali (sat) language.
Several enhancements have been made to the Inactive CSS styles feature. This feature assists in identifying CSS properties that have no effect on an element. Pseudo-elements such as ::first-letter, ::cue, and ::placeholder are now fully supported.
The JSON viewer is particularly useful for debugging REST APIs, as it displays formatted JSON responses. Now, if the JSON is invalid or broken, it automatically switches to a raw data view, improving the user experience.
Grouping of items in an array (and iterables) is now easier by using the methods Object.groupBy or Map.groupBy.
Hmm, only system fonts doesnt seem to help? Wouldnt that circumvent having the browser in a fake environment like Torbrowser does that, with the same fonts?
The only thing I want is proper support for desktop addons on mobile.
I’m guessing way less than 1% of people would use mobile extensions. I personally do but I don’t think most people use chrome on mobile because of the lack of full extension support on mobile Firefox (which btw is coming). I think people use chrome because “everyone else does”.
People use whatever ‘Internet icon’ came with their device and live their ignorant, but happy life :)
I think you’re underestimating how valuable tab groups are to people. I would make a full switch if Firefox could offer that feature on mobile in any reasonable way. Since it’s already a desktop extension, I’m just waiting for them to be made available on Android
@TrickDacy @parpol I just wish that in 2023, Apple would relinquish their claw-like grip on mobile browsers on iOS. Give me ACTUAL Firefox, please.
You can use a couple already in the nightly builds of both firefox and the respective add-on
Sure, but not even close to all. It’s been literal years since the change. I was understanding at first, but now it’s just becoming frustrating. Things that are very easy in desktop Firefox just isn’t possible on mobile Firefox. And yes, I am running Firefox nightly and custom collections for my extensions on mobile.
