- Microsoft Edge tells testers that their old extensions, like UBLOCK -EXPRESSION, are no longer supported
- However, this seems to be a trait that was accidentally introduced to the earliest test version of Edge
- Don’t be under any illusions that this is not happening in the end but to look at Microsoft’s timeline, it feels like it’s still pretty gone
Microsoft Edge just received a change in testing that makes it look like the browser can soon follow in Chrome’s footsteps in trenching certain extensions – especially including a popular ad blocker, Ublock origin – but in fact this is not the case.
Granted, it’s a somewhat worrying development for some people – and that points the way for the future, I wouldn’t claim that. However, as the discoverer of the change for the earliest test version of Edge ensures us, it is likely that something that is automatically passed through the test premature, rather than a intentional move from Microsoft.
As highlighted by Leopeva64 on X in the submissions below, the Canary version of Edge recently received a new preview-building, and it produces a message of some extensions (additions to the browser) that are no longer supported and instructs users to remove them.
1/2 A message that some extensions have been disabled because they are no longer supported has emerged after installing the latest canary building, but I think this is one of the unexpected changes coming from upstream chrome: pic.twitter.com/blwpi5onyhFebruary 24, 2025
This happens with Ublock origin as mentioned, and other extensions built using Manifest V2. This is the platform on which these browser extensions are built and it has been upgraded to manifest V3 – a change long in the works, and one that has already come into play for Chrome (where I think the release version of Google’s browser, not just test buildings).
What seems to have happened here is because Edge is built on chrome – the same engine as Google Chrome – the change has been passed through automatically.
In other words, Microsoft did not think to adopt this and the move will (presumably) be corrected soon enough.
It is worth noting that even in this (seemingly erroneous) form in testing is only extensions that are seized from the Chrome Web Store, and not the official additions of the Edge Store.
Analysis: A big shift for all chrome browsers (albeit with some brave resistance)
All that said, we do not know for sure if that is what has actually gone here – Leopeva64 says they ‘think’ this is the case and it seems likely.
Mainly because Microsoft has a schedule for migration from Manifest V2 to V3 extensions with edge, and currently, as Neowin marked up, there is no fixed date to ditch the older V2 add-on-time frame remains marked as TBD (to be determined). It is both in terms of dumping these V2 extensions for consumers and businesses (the latter will happen later).
But there is A schedule, and this V2 to V3 migration happens, makes no mistake, which will mean that the traditional version of Ublock origin – which is the extension that most people are bothered by losing support – gets the elbow from the edge eventually. It’s just that it probably won’t be for some time yet.
In his support document about the time frames involved, Microsoft notes: “The Microsoft Edge team is currently updating this MV3 migration timeline.” So we might hear more about the exact schedule soon enough.
All web browsers built on chrome will eventually be affected by the change Google has initiated here, although some developers will try to swing around it as best they can.
For example, the manufacturer of the brave browser, another of the chronicles, has said it will use patches to try to keep certain popular V2 extensions alive, even after support is fully drawn by Google (and that includes Ublock origin). Although it will be implemented on a ‘best effort’, there are no guarantees.
On one last note it is also worth remembering that there is already a V3 version of Ublock origin in place, but it is a ‘Lite’ takeover of the ad blocker, because with V3 it is simply not possible to offer the same options.
Google’s major transition to V3 is done to get what the company claims is better security and performance for browser extensions over V2, but not everyone agrees with this mindset, to say the least.
