Avast aquired "i-dont-care-about-cookies"

This is what I see on Chromium with the extension disabled. A cookie nag...
No change in behaviour and appearance of the addon badge and dropdown menu after reloading.
And I don't intend to install Vivaldi just to test this.

https://dl.dropboxusercontent.com/s/mqtp61ru4oe9sv4/screenshot_20221102.png

I still don't quite understand his issue either.
And since the developer isn't aware (yet) of this thread, I would suggest filing issues on GitHub.

 

I was just thinking, maybe the difference in behaviour can be due to the fact it's a Manifest V3 extension?
The one I use in Chromium is Manifest V2, built from current source by myself (renamed 'manifest_v2.json' to 'manifest.json').

 

Also, to avoid glitches, be sure to restart your browser after an update of the extension.

 

thats not needed because extensions are not allowed to work that deep, for no browser. a simple page reload without cache (ctrl+F5) is all you need.

for vivaldi - vivaldi is special because of his internal blocker. its none of the known extensions, its something of their own, like firefox having its own. you can take it, or leave it.

for the manifest. his src include files and code for both, but at least the definition for v2 and v3 are different and need a different code, its not that simple with renaming the manifest file. compare yourself.

concerning MV3 there is a timeline where new MV2 extensions are no longer accepted, only MV3, and how long MV2 extension could be updated.

MV3 is ready for triage in firefox, since v101 developer
https://extensionworkshop.com/documentation/develop/manifest-v3-migration-guide/
mozilla will maintain MV2, maybe until the bitter end.

the major problem i consider is that authors are forced to develop for both platforms, or, if it exist no problem to do same for both MV3 is solely. in case for uBo gorhill can settle on MV2 or MV3, in case of MV3 i think he will lose users.

 

Well, I had to rename one of them, because there is no 'manifest.json' file at all in 'src' from GitHub.

The content of the .crx file from the Web Store is like this:



Wherein 'manifest_v3.json' and 'manifest.json' have the same MD5-sum.

In the file './data/background.js' there is indeed separate code for MV2 and MV3 (search for 'manifest').

 

Yes exactly, with IDCAC you can disable the extension no matter if cookie dialogs are actually being blocked or not. With ISDCAC this can't always be done.

Open the cbnc.com site that I provided, then you will indeed see the disable option in the menu. But then navigate to other pages on cnbc.com, and all of a sudden the disable option will disappear. In fact, on beursgorilla.nl I don't get to see the green checkmark but the cookie dialog is blocked anyway. Problem is that when you navigate to other pages on this site, eventually the disable option will once again magically disappear overtime. There is something seriously wrong with the ISDCAC extension on Vivaldi.

https://www.cnbc.com/2022/11/02/sto...vs-estee-lauder-canada-goose-and-others-.html
https://www.beursgorilla.nl/Nieuws/default.aspx

 

BTW, I haven't got a clue if Manifest V3 might play a role. However, I did just notice that by mistake the IDCAC filter in uBlock Origin plus the adblocker in Vivaldi was still active, so I will test again. Perhaps this weird behavior of ISDCAC might disappear.

 

BTW, even when Vivaldi's adblocker and the IDCAC filter in uBlock is disabled, ISDCAC still acts weirdly. Sometimes it will show the disable option in the menu, and then after a while it will magically disappear on the same domain name. This extension seems to be buggy on Vivaldi, I will now also test it on Edge and perhaps Firefox.

 

It is advised not to use more than one ad blocker.

FWIW, I didn't see weird behaviour in Firefox and Chromium here on those sites.
Only glitch was on www.beursgorilla.nl with Chromium, where there was no green check mark, using the MV3 version of ISDCAC from the Web Store.
My self built MV2 version did have the check mark.

 

i know, i saw. because src let user decide which one he wants.

want mv2? just rename manifast_v2.json to manifest.json
want mv3? just rename manifast_v3.json to manifest.json

but at least the code behind is complete different. mv3 do not work as mv2, not even close.

 

I have tested it once again and it seems to be a problem with ISDCAC on Vivaldi. I couldn't test it on Edge since I'm using an old version and ISDCAC isn't supported. But on Firefox it seemed to behave normally. To clarify, on Vivaldi it does seem to block the cookie dialogs, but the extension-icon seems to behave abnormally.

So in short, once we disable ISDCAC, we should see the red stop sign. If a cookie dialog is successfully blocked, we should get to see a green checkmark. And in my view, we should always see the same options in the left click menu, like the ability to disable this extension on a certain site and the settings option. Even if ISDCAC isn't supported on a certain website.

 

I installed Vivaldi to test.

On cnbc.com everything appeared to be normal.
On beursgorilla.nl there was no green check mark, just like in Chromium.

Sometimes a reload is needed to see the options in the left click menu again ---> bug.

My self built MV2 version behaved normal in Vivaldi and had the green check mark on beursgorilla.nl.

 

On Wilderssecurity.com, for which the extension has no rule, I see all the options in the left click menu.

 

OK so you're getting to see the same as me, I also need to reload the page to see all of the options of the left click menu. Earlier I said right click menu, but this was a mistake, I obviously meant the left click menu, I edited the post.

The bug is that these options may disappear out of the blue after some time. So on Vivaldi there is something wrong, I will also report this on the Vivaldi forum since uBlock also doesn't show the purple icon when JS is disabled on certain websites.

 

This bug in the issue tracker at GitHub seems related:
https://github.com/OhMyGuus/I-Still-Dont-Care-About-Cookies/issues/362

 

OK, so it's indeed a bug. I didn't know that MV3 played a role in this. Hopefully it will be fixed soon, because it's a bit amateuristic if an extension doesn't completely works correctly.

 

ISDCAC v1.0.9 for Chromium released.
Download from GitHub (not yet in Web Store).

ISDCAC v1.0.10 for Firefox released.
On AMO.

 

Does anyone know where ISDCAC stands in number of blocked websites compared to original IDCAC?

 

No idea about the exact number at the moment, but more sites should be supported since it adds IDCAC's sites to its own.

 

OK, anyway better to test both. IDCAC is still being maintained so only a live comparison can show which one blocks more.

 

OK, I tested both IDCAC and ISDCAC for two days and they behaved exactly the same in terms of blocking, i.e. neither missed cookie and if they did, then both. However IDCAC performed better actually faster. ISDCAC was slow in blocking cookie warnings on some webs. I think the original one is better integrated in Opera.

 

I think the culprit here is, that IDCAC is still a Manifest v2 extension.
Manifest v3 extensions, like ISDCAC still face issues unfortunately.
IDCAC will have to move to MV3 in the near future. If not, Google will remove it.
https://developer.chrome.com/docs/extensions/mv3/mv2-sunset/

If you want, you can test ISDCAC as MV2 extension.
Follow these steps:

• Download ISDCAC- chrome-source.zip from Releases.
• Extract the .zip file with 7Zip or WinRar to a folder.
• Delete 'manifest.json' and rename 'manifest_v2.json´ to 'manifest.json'.
• Go to the browser address bar and type: opera:extensions.
• Check the “Developer Mode” button to enable it.
• Click on the “Load Unpacked Extension…” button.
• Select your extension’s directory.

You will see 'Errors', but they can be neglected.

 

Yes, that explains it. The same (slow blocking) applies also to the AG MV3 extension.

Thanks!

 

One caveat, you'll have to update manually when there is a new release.

This is why I use MV2 extensions whenever possible for as long as they work.
uBlock Origin comes to mind.

Fortunately Firefox is my main browser and Mozilla intends to keep supporting them.
ISDCAC on Firefox is still fast.

 

Yes, I know. It's an acceptable price

I read somewhere that Google is going to postpone MV3 so hopefully there will be enough time to hone MV3 extensions.