-
Notifications
You must be signed in to change notification settings - Fork 142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ghostery Extension No Longer Working #1550
Comments
Thanks for reporting! I cannot reproduce myself, but from the screenshot it looks like a bug. From the looks of the screenshot, I tagged it as Chrome (hope I guessed right?). However, we also got a recent report for Opera, so it is not clear if it is isolated to Chrome. |
We are still retrying to reproduce. What I believe we can rule out is that it relates to the problem on Opera. (Opera uses already Manifest V3 and the DNR API. Looks like there is a bug in the browser. Only uninstalling and reinstalling helps. For details, see #1554) The Chrome extension, however, is still on Manifest V2 and does not use the DNR API. Thus, these must be different problems. |
I just double checked on my computers and I don't see this issue anymore. Ads and trackers are now being correctly picked up in my browser plug-in for Chrome and it is behaving as expected. I just checked the version number of my Ghostery plugin and it is 8.12.9 running on Chrome 124.0.6367.61 edit: |
Chrome platform migrated to v10. Feel free to re-open if the issue is still valid. |
Sometime within the past week the Ghostery extension is no longer blocking ads - I first noticed it on several web pages such as SlickDeals where now i'm getting presented with a sidebar full of ads as if I was not running Ghostery . When I open the Ghostery panel, it doesn't show any trackers / advertising as blocked and it all shows as "Unidentified"
I have tried to update my tracker list several times and still not getting any blocking. Not sure what is going on or what is causing this, perhaps a malformed blocklist?
The text was updated successfully, but these errors were encountered: