AFAIK some of the other chromium forks (brave and/or edge?) were committed to backporting manifest v2 (or more specifically the webRequestBlocking API) for future chromium versions.

▲

bjord 2 hours ago | parent [-]

this is not correct. neither brave nor edge has committed to that.

as of yet, there's no (publicly stated) contingency plan if the upstream mv2 code is excised, but I could be mistaken.

	▲	rpdillon 12 minutes ago \| parent [-]
		Brave has integrated uBO directly into their core logic. Visit brave://settings/extensions/v2 and you can download it, even with no MV2 support. I'm not aware of any other browser adopting this approach.