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.
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.
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.