- Messages
- 6,176
@Vendor-Lazarus posted these links to show how much Chromium code is in Firefox:
https://archive.ph/odk9n, https://en.wikipedia.org/wiki/WebRTC, https://archive.ph/3zDI5, https://archive.ph/pdS87, https://archive.ph/kqYWs, https://archive.ph/RtCSO, https://archive.ph/nPaeN, https://archive.ph/lt9T7
I will be going through this list and seeing what is what.
Manifest v3.x
Firefox is indeed incorporating this standard BUT they are still supporting the Manifest v2.x standard and they have also made their own significant alterations to Google's more asinine proposals in v3.x.
WebRTC
Originally bought by Google and then released by them fully open source in 2011, the Internet Engineering Task Force (IETF) and World Wide Web Consortium (W3C) took this project and developed it into a standard where it has stayed ever since. I would also like to note that this was back when Google was still kind of a force for good. Before the fall...
Polymer (library)
Web Components, the pieces of such later integrated into a single library called Polymer, is indeed mostly developed by Google, it looks like it's just an easy way to build web pages. I have no idea why it would be included in Firefox, or even any browser for that matter. This is much more a backend web developer tool than anything.
Firefox uses Google's Geo Location Services
In
Skia Graphics Engine
This is an open-source 2D graphics library developed mainly by Google. With this one, there's no argument from me here. This is definitely a Chromium component in Firefox and should probably be examined by Firefox devs for future excision. In Mozilla's defense though, this is actually an OLD library first acquired by Google in 2005 and then released as open source in 2008.
Google Widevine Content Decryption Module (CDM)
This is a DRM decryption module that used to be run in a sandboxed mode by Firefox but also no longer seems to be in Firefox whatsoever to my knowledge. Checking the Plugins page for me only lists "OpenH264 Video Codec by Cisco Systems".
Safe Browsing/Firefox Phishing Protection
A component that checks a site against Google's generated and downloaded list of bad sites as far as I can tell. This is definitely Google-backed, so it's valid. Not a very important component though and you can switch it off in
Irregexp
Forked from Google's code a while ago by Mozilla, and then reforked again when their implementation was old and busted. Not sure if this is still used in Firefox anymore these days, but assuming it is, this is fair.
https://archive.ph/odk9n, https://en.wikipedia.org/wiki/WebRTC, https://archive.ph/3zDI5, https://archive.ph/pdS87, https://archive.ph/kqYWs, https://archive.ph/RtCSO, https://archive.ph/nPaeN, https://archive.ph/lt9T7
I will be going through this list and seeing what is what.
Manifest v3.x
Firefox is indeed incorporating this standard BUT they are still supporting the Manifest v2.x standard and they have also made their own significant alterations to Google's more asinine proposals in v3.x.
WebRTC
Originally bought by Google and then released by them fully open source in 2011, the Internet Engineering Task Force (IETF) and World Wide Web Consortium (W3C) took this project and developed it into a standard where it has stayed ever since. I would also like to note that this was back when Google was still kind of a force for good. Before the fall...
Polymer (library)
Web Components, the pieces of such later integrated into a single library called Polymer, is indeed mostly developed by Google, it looks like it's just an easy way to build web pages. I have no idea why it would be included in Firefox, or even any browser for that matter. This is much more a backend web developer tool than anything.
Firefox uses Google's Geo Location Services
In
about:config
, there is a setting called geo.provider.network.url. It's claimed that Firefox has this defaulted to https://www.googleapis.com/geolocation/v1/geolocate?key=%GOOGLE_LOCATION_SERVICE_API_KEY%
. I confirmed this with my MX23/Debian 12 repository-installed edition of Firefox 135.x, so this is all true. However, keep in mind a couple things. For one, Firefox should by default explicitly ask you if you want to submit your location to a website at all if the site asks for it. For two, you can change this setting to https://location.services.mozilla.com/v1/geolocate?key=test
, or data:application/json,{"location": {"lat": 40.7590, "lng": -73.9845}, "accuracy": 27000.0}
for a specific location. For three, is submitting your IP to Mozilla really any more private? One might actually argue that it may ironically be MORE private to use Google as your request will mix in and be lost in a sea of a million requests. And finally, I'm not sure this even counts as this is not any part of Firefox's internal web engine and can also be completely disabled permanently without incident.Skia Graphics Engine
This is an open-source 2D graphics library developed mainly by Google. With this one, there's no argument from me here. This is definitely a Chromium component in Firefox and should probably be examined by Firefox devs for future excision. In Mozilla's defense though, this is actually an OLD library first acquired by Google in 2005 and then released as open source in 2008.
Google Widevine Content Decryption Module (CDM)
This is a DRM decryption module that used to be run in a sandboxed mode by Firefox but also no longer seems to be in Firefox whatsoever to my knowledge. Checking the Plugins page for me only lists "OpenH264 Video Codec by Cisco Systems".
Safe Browsing/Firefox Phishing Protection
A component that checks a site against Google's generated and downloaded list of bad sites as far as I can tell. This is definitely Google-backed, so it's valid. Not a very important component though and you can switch it off in
about:config
and in the regular Firefox settings.Irregexp
Forked from Google's code a while ago by Mozilla, and then reforked again when their implementation was old and busted. Not sure if this is still used in Firefox anymore these days, but assuming it is, this is fair.