2.2.0 code?

[nascentt]

Hi I noticed the extension has been updated on the chrome web store to version 2.2.0 and now has new permissions to 3rd party sites. I can't see any updates to the repo since October last year, and the last version released here is 1.2.1

[DavG25]

Hi, thanks for your interest in the extension

This GitHub repo refers to the Manifest V2 version of the extension, which is published on Firefox as version 1.2.1, soon to be updated to 1.2.2 to receive the latest configuration to block cookie consent popups

The plan is to eventually also publish the Manifest V3 version on GitHub

As for the new permission in the 2.2.0 version, it is used to fetch the latest data used to block cookie consent popups (as specified in the changelog), to be more specific, the extension sends a GET request to the API endpoint https://www.davg25.com/app/cookie-consent-popup-blocker/api/extension/update and receives a JSON response containing the following data:

• Configuration for the SOCS cookie
• Configuration to detect cookie consent popups, for example by checking if an element exists with document.querySelector()
• Additional configuration used to determine the fetch update interval and if the received data is compatible with the current extension version

This automatic update feature was added in version 2.2.0 to make sure the blocking method is always up to date without the need for a full extension update, in particular to avoid long wait times when the extension is updated for the sole purpose of changing a value to detect and block cookie consent popups, for example:

Without automatic updates

• Extension does not detect cookie consent popups anymore using document.querySelector() with the value div[aria-modal]
• The extension is updated to detect cookie consent popups again, this time using document.querySelector() with the value div[role=dialog]
• The update is submitted to the Chrome Web Store
• Google reviews the changes made to the extension and approves the update (this can take several days)
• The updated extension is released to all users

Result: this process can take up to two weeks

With automatic updates

• Extension does not detect cookie consent popups anymore using document.querySelector() with the value div[aria-modal]
• The API endpoint tells the extension to use document.querySelector() with the value div[role=dialog] instead
• All users receive the latest blocking method

Result: this process takes around one hour

If you want to opt out of the update feature, you can do so directly in the extension settings by turning off the following setting: Doing so will block any connection made to the update endpoint

You can also disable access to the update endpoint by turning off the related permission in the browser extension settings:

If you're configuring the extension with policies, you can disable the automatic update feature by setting the policy EnableAutoUpdate to false, this will also block any connection to the update endpoint

Alternatively, you can still use this GitHub version on Google Chrome until Manifest V2 is phased out completely (visit this page for more information)

[nascentt]

Thank you for the very detailed and informative reply.

It's also great to hear the manifest v3 version of the script will also eventually be open source!

Appreciate your hard work.