Bitdefender Anti-tracker Wants access to this site (every site!)

Anthony42

I recently found that the Bitdefender Anti-tracker extension was preventing a particular page from working in Microsoft Edge, so I added the page to it's exception list, which fixed the problem.

However, ever since then, the extension doesn't seem to work on any page when it is first loaded until the page is refreshed through the extension itself. At least, the icon in the browser doesn't show the number of trackers blocked. When I hover the mouse over it, it shows "Bitdefender Anti-tracker Wants access to this site":

Clicking on it pops up a little window saying "Reload this page to apply your updated settings on this site" with Refresh and Cancel buttons:

Clicking Refresh refreshes the page and the extension starts working normally, showing the number of blocked trackers on the icon. Hovering the mouse over the icon now shows "Has access to this site" rather than "Wants access":

And now, clicking the icon shows the full info as it always used to do:

But the next time I load the same page, or any page, it's back to "Wants access to this site" again until I select it and click "Refresh".

I'm sure it never used to behave like this. Is this normal? It looks as though the anti-tracker isn't doing it's job until I click it's refresh button (just refreshing the page in the browser doesn't make any difference).

These screenshots were taken from x.com, on which the extension used to block hundreds of trackers as soon as the page was loaded according to the number shown on the icon. Now it doesn't appear to block anything unless I click on it and select refresh. Which has to be done every time on every page.

Is there a way I can get it to work properly again without having to manually activate it for every page load?

Anthony42

Ah, I think I may have just found the answer myself.

Right-click the icon and select "This can read and change site data >" from the drop-down menu. This was set to "When you click the extension". Presumably this changed when I added the a site to the exception list.

I've changed it to "On all sites" and it seems to be behaving normally again.

Flexx

Nice to know you figured out the resolution by yourself. Since the issue has been resolved, this post is now closed to further comments.

Regards