There was a recent update pushed to google a few minutes ago that makes Consent-O-Matic run in circles.
Instead of clicking the "Reject all" button, it clicks "More options", and does something to that page. When reloading the page Google's bad-faith consent banner shows up again, and Consent-O-Matic repeats the process. The result is a never ending loop where the browser just cycles between the popup page and the consent "options" details page.
So the issue is two fold:
Consent-O-Matic clicks the wrong button (should click Reject all).
Google seems to not persist the user's decision, so throws up the same consent popup on next page load (likely a bug on their end they just trigger-happied pushed out by mistake)
The former can be fixed by this project, and if it is, at least Google search can become usable until they (hopefully) fix the persistence issue on their end, without having to disable Consent-O-Matic altogether.
There was a recent update pushed to google a few minutes ago that makes Consent-O-Matic run in circles. Instead of clicking the "Reject all" button, it clicks "More options", and does something to that page. When reloading the page Google's bad-faith consent banner shows up again, and Consent-O-Matic repeats the process. The result is a never ending loop where the browser just cycles between the popup page and the consent "options" details page.
So the issue is two fold:
The former can be fixed by this project, and if it is, at least Google search can become usable until they (hopefully) fix the persistence issue on their end, without having to disable Consent-O-Matic altogether.