search

eylenburg / eylenburg.github.io

https://eylenburg.github.io/
Creative Commons Attribution Share Alike 4.0 International
119 stars 11 forks source link

Browser comparison inaccuracies #1

Closed 29edde2e closed 2 years ago

29edde2e commented 2 years ago

I noticed some inaccuracies in your browser comparison, mainly:

That you can't run Firefox on Chrome OS, you can. That you can't view and save files in cache, you can by navigating to about:cache. That you can't upload files from the clipboard, you can with an extension. That Firefox includes an in-browser proxy or VPN, this isn't entirely true. Mozilla VPN does exist, but it isn't included with the browser. Firefox Private Network also exists, but it's an optional extension and not included by default.

"Ability to change tab bar position " should say "Dropped (v29) (ext.)". You could choose between tabs on top/bottom before Australis.

The "Option to disable hyperlink auditing pings" result is wrong, Firefox doesn't enable the ping attribute by default. You have to enable it in about:config. It'd be more accurate to say Yes (disabled by default) (hidden) since the list is comparing defaults. Or rename that line to be clearer: supports hyperlink auditing pings

Your point about "Ad blocking" is interesting. What you're referring to as "Ad blocking" should really be called "Cosmetic ad blocking". Firefox blocks ads through Enhanced Tracking Protection but does not use filter lists or scriptlets to hide ad elements themselves. It should be split into two columns ideally.

Additionally, "Ability to modify browser's UI elements" is wrong. You can edit the interface by opening the application menu > more tools > customize. It should either be renamed to "Ability to modify browser's UI elements with CSS" or split into different columns.

Safari does support CNAME Uncloaking

eylenburg commented 2 years ago

Thank you for the suggestions, that's really helpful. I have implemented all of them. Just on the hyperlink auditing I'm not sure what the default behaviour of Firefox is (including on Android). In 2019 they announced to enable it by default (e.g. here: https://www.bleepingcomputer.com/news/software/mozilla-firefox-to-enable-hyperlink-ping-tracking-by-default/ ) but I'm not sure if they backtracked?

29edde2e commented 2 years ago

Yeah this one was confusing. I asked a member of the Mozilla webcompat team and they said Firefox has it disabled by default. I just tested in a new profile and the pref (browser.send_pings) was false so I think they backtracked and never did it.