A user, ganncamp, reports that Chrome (specifically a secure fork used by their company) is falsely indicating that ads have been blocked on their Discourse instance, despite there being no ads. hello-smile6 suggests ignoring the warning as a false positive, but ganncamp is concerned about user confusion. The issue appears to occur on individual topic pages but not on list pages. hello-smile6 notes they cannot reproduce the issue and asks if it occurs on a standard Chromium build, referencing a related community topic here.
Chrome (okay, the “secure” fork of Chrome my company uses) keeps telling me it blocked ads on our Discourse instance:
But we don’t have any ads at all.
We’ve got a few plugins and components installed in our public community, but I get the same warning on our internal instance as well, and AFAIK it’s pretty vanilla.
Is anyone else seeing this? Any ideas how to ‘fix’ this?
If there are no ads, could you simply ignore that, since it is a false positive?
I can ignore it all day long. It’s my users I’m concerned about 
Just opened your public site, and I can’t easily reproduce the issue. Is there a specific page that is affected?
Go to a topic. It doesn’t seem to happen on the list pages
I just read through this topic, and I can’t reproduce the issue. Does the issue occur on a normal Chromium build?
There’s what I get for assuming. Thanks!
