(Discussion) Manifest V2 Deprecation - What do we do?

[Metrokoto]

Preliminary checklist

• [X] I have read the README
• [X] I have searched existing issues for my feature request. This is a new issue (NOT a duplicate) and is not related to another issue.
• [X] I have searched wont fix issues and this request is not among them
• [X] This is a feature request for the Cromite browser; not the website nor F-Droid nor anything else.

Is your feature request related to privacy?

Yes

Is there a patch available for this feature somewhere?

N/A

Describe the solution you would like

The APIs for Manifest V2 which is required for many extensions like uBlock Origin will be removed from the Chromium source code some time next year, what actions are we going to take, in regards to this?

Brave, for example, is using a policy to extend the usability of MV2, but this seems to only be a temporary measure: https://brave.com/blog/brave-shields-manifest-v3/

I would therefore recommend that @uazo (and anyone with knowledge of Chromium's inner workings) look into creating a patch for Cromite to completely bypass the removal of Manifest V2, ready for when Google fully removes the API, so we can patch it back in immediately with no interruptions to end users.

Describe alternatives you have considered

N/A

[uazo]

the timeline is set for June 2025 . there is some time to think about it.

[Metrokoto]

the timeline is set for June 2025 . there is some time to think about it.

I suggest enabling ExtensionManifestV2Availability going forward for now, until we come up with a solution, as that will give us an extra year.

That appears to be what Brave, Edge and Opera are doing.

[Metrokoto]

https://www.reddit.com/r/chrome/comments/1dln9ev/tutorial_extend_manifest_v2/

[uazo]

I suggest enabling ExtensionManifestV2Availability

already in operation see chrome://policy/

[Metrokoto]

I suggest enabling ExtensionManifestV2Availability

already in operation see chrome://policy/

Brilliant! Apologies, I didn't think it was set, as uBlock gave me a MV2 error message when I installed the latest developer edition the other week.

[Metrokoto]

the timeline is set for June 2025 . there is some time to think about it.

I agree, however I personally believe deciding on a solution should be done sooner, rather than later, if Google Graveyard is anything to go by, we can't trust that Google will abide by their June 2025 deadline.

[Metrokoto]

@uazo A finalized solution may be needed sooner than we think. Chrome Canary is testing removal as we speak.

Source: https://youtu.be/TO48wxdjWMg

[Metrokoto]

Something to note, another Chromium fork, Supermium, has plans, like we do, to continue supporting Manifest V2 post-removal.

Perhaps this could be a chance for wider collaboration?