InformAction Forums

Chrome (Win64 128.0.6613.120) is warning me that NoScript "may soon no longer be supported".

Checking if that's the case.
-jon

The Chrome Web Store page for NoScript has a similar warning:

This extension may soon no longer be supported because it doesn't follow best practices for Chrome extensions.

Aphabet would really like to interdict any active content blockers and is happy to warn as much user traffic off as possible with these boilerplate alarms.
In particular I enjoy the humour in the idea that the browser could suggest a suitable alternative to simply the best security extension for modern browsers
i doubt that the way NS works in Chromium now is going to be much changed with the change to the new
version of Chrome and I'm sure that Giorgio will have any minor changes covered when the hammer falls.

For context, this warning is about Manifest v3, which was discussed some in viewtopic.php?t=25393

Not sure what is the current status of NoScript regarding Chromium/Chrome's Manifest v3?

ghacks.net - Google is killing uBlock Origin in Chrome, but this trick lets you keep it for another year

I use this tip from that page which will allow me to continue using uBlock Origin and Noscript in Google Chrome until June 2025
the "extension may soon no longer be supported" message no longer appears in the Chrome browser extensions page when I use this tip

barbaz wrote: ↑Wed Sep 11, 2024 7:30 pm Not sure what is the current status of NoScript regarding Chromium/Chrome's Manifest v3?

Looking through the changelog today, it looks like Giorgio is working on MV3-compatible code and perhaps plans to release that in a future v12 version.

But he seems to stay very quiet about these things. I think it would be very hard to replicate all the current NS functionality with a MV3-compatible version, I guess we will have to wait and see.

In the meantime I'm using the enterprise policy to keep MV3 extensions running until June.

I have about a half-dozen of them that are not MV3 compatible yet, most may never be.

pjk wrote: ↑Thu Oct 31, 2024 11:51 pm

barbaz wrote: ↑Wed Sep 11, 2024 7:30 pm Not sure what is the current status of NoScript regarding Chromium/Chrome's Manifest v3?

Looking through the changelog today, it looks like Giorgio is working on MV3-compatible code and perhaps plans to release that in a future v12 version.

But he seems to stay very quiet about these things. I think it would be very hard to replicate all the current NS functionality with a MV3-compatible version, I guess we will have to wait and see.

an upcoming version 12 alpha is scheduled to be released before year 2024 ends as noted here

NoScript 12 alpha, which is going to be released before the end of 2024, will be Manifest V3 and Chrome compatible out of the box.

Looks like v12 was temporarily released (at least for Chrome) and it had a nasty bug so Giorgio rolled it back. (Tho named 12.0.1 to keep the Chrome store happy about version numbers that are not allowed to go "backwards".)

Except for me, it has still hosed my copy of Vivaldi despite running the "rolled back" 12.0.1 version, blocked logins basically everywhere.

I'm now frantically exporting my rules to a Firefox instance so I can continue using the WWW.

Looks like 12.0.2 has fixed the 12.0.1 problem.

Now to see about the MV3 things..

12.0.2 works okay in Chrome & Vivaldi (and possibly Brave & Opera) but not working on some sites on MS Edge as reported here

4td8s wrote: ↑Sat Nov 23, 2024 5:44 pm 12.0.2 works okay in Chrome & Vivaldi (and possibly Brave & Opera) but not working on some sites on MS Edge as reported here

I'm having intermittent problems on various sites on Vivaldi as well.

For example, used to be able to get past the Google captcha by enabling www.google.com temporarily (google.com is globally disabled on my systems, only certain subdomains enabled by default), but now I cannot get it to work at all sometimes.

Today it wouldn't work for blood or money, left to try on a different browser (Firefox), wouldn't work there either.

Then came back to Vivaldi and it was working again.

Also, the "disable all temporary permissions" button does not seem to be working, or is not working consistently.

Today it wouldn't work for blood or money, left to try on a different browser (Firefox), wouldn't work there either.

NoScript 12.x does not apply to Firefox.
So if FF was also not working, it was not related to NoScript 12.x.