Skip to content

Manifest V2 updates in Chrome Web Store #359

@ShivanKaul

Description

@ShivanKaul

Will NoScript continue to publish updates for Chrome Web Store once MV2 extensions are deprecated? Brave browser would like to support it since we plan to allow MV2 extensions but it would be great we can update via Chrome Web Store, at least until Enterprise policy supports it.

We're experimenting with a feature flag (brave://flags/#brave-extensions-manifest-v2) on Brave Nightly that will add a brave://settings/extensions/v2 page where users can manually install NoScript and a few other extensions.

Activity

ryanbr

ryanbr commented on Jun 1, 2024

@ryanbr

For reference; what it looks like currently

adguard-mv2

hackademix

hackademix commented on Jun 1, 2024

@hackademix
Owner

Hello, the transition to Manifest V3 is in undergoing, but the necessary APIs are not there yet so it will take some more time.

Thanks for caring!

ryanbr

ryanbr commented on Jun 1, 2024

@ryanbr

Could continue to support MV2 extensions on Chromium if possible

R-Adrian

R-Adrian commented on Jul 17, 2024

@R-Adrian

Currently running beta: Google Chrome Version 127.0.6533.43 (Official Build) beta (64-bit)

Chrome 127 is scheduled to be released as stable for general availability sometime next week.
(It is supposed to be released today as early stable according to the release dashboard)

...and the extensions management page already shows:
"These extensions may soon no longer be supported"

image

Vardziya

Vardziya commented on Aug 5, 2024

@Vardziya

Are there any updates about support of Manifest v3?
I dont'want back to Mozilla from Chromium ((
image

Chromium 129.0.6639.0.

sometowngeek

sometowngeek commented on Sep 8, 2024

@sometowngeek

Any updates? :)

I'd hate to see this extension go away... I find it very useful in protecting my privacy and helping with my ADHD (rotating ads are very distracting)

hackademix

hackademix commented on Sep 8, 2024

@hackademix
Owner

JShelter 0.19, released last month, is a proof of concept / test bed for the MV3-compatible NoScript Commons Library, which NoScript is largely based on .

Last week I've merged the NSCL mv3 branch into main, and at this moment I'm both maintaining NoScript 11.x and working on a mv3-compatible NoScript 12.

Please notice, though, that the extensions APIs on Chromium are already inferior to those offered by Firefox (even on MV2), causing NoScript and other Privacy Enhancer Tools (PETs) to suffer limitations on Chromium-based browsers.

Therefore, even though a MV3-compatible NoScript is coming by the end of the year, I still strongly suggest to switch to Firefox.

ghost

ghost commented on Nov 13, 2024

@ghost

@hackademix, would you consider maintaining both a MV2 and MV3 version? This would allow browsers like Brave, as mentioned by @ShivanKaul and others that continue supporting Manifest V2, to use the slightly more powerful version of NoScript for chromium-based browsers.

hackademix

hackademix commented on Nov 18, 2024

@hackademix
Owner

I'm both maintaining NoScript 11.x and working on a mv3-compatible NoScript 12.

And here it is โœŒ๏ธ

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @hackademix@ryanbr@ShivanKaul@sometowngeek@R-Adrian

        Issue actions

          Manifest V2 updates in Chrome Web Store ยท Issue #359 ยท hackademix/noscript