For a while now the transition away from Manifest V2 (MV2) to MV3 has been on-going and it looks like it is entering its final phase of deprecation, at least, in the case of Google Chrome. A recent discussion thread in the w3c WebExtensions Community Group GitHub repo has highlighted how the latest and upcoming versions of the most popular browser are expected to be its final releases with support for MV2 extensions.
What this essentially means is that the tricks and bypasses that were used to keep MV2 extensions like uBlock Origin and others alive will not work any more on Chrome, or at least not for very long. For example the Windows Registry mod that could extend MV2 availability will cease to function after Chromium version 151.
Fun fact: many sites that say that they don’t support firefox lie, their sites usually support it but they never tested it or they deem firefox “less secure” or some bullshit, but with an useragent spoofer, they will work
(Not all sites ofc)
Removed by mod
I think you should read my reply again, slowly
I’m not talking about sites that claim not to support FF. I’m talking about sites that have broken features when visited in FF.
Do you have any example? Can you send any link? I never experienced those problems myself so i want to try
Chrome is doing the same thing as Internet Explorer did by not following web standards. There are several websites I have used where the payment process or uploading process only worked in chrome.
Again, this is a problem with chrome doing things that breaks consistency between browsers that are supposed to be following the same web standards.
This should be seriously addressed tbh, someone should make an european initiative to sanction whoever don’t follow web standards; I’d make it but i am not really the right person to do it, sadly
This is very well documented, and a very common experience.
They were talking about exactly this on late night linux podcast just last week.