New issue
Advanced search Search tips

Issue 751671 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner: ----
Closed: Aug 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 737201



Sign in to add a comment

Chrome says localhost doesn't comply with Better Ads Standards

Reported by kamoroso...@gmail.com, Aug 2 2017

Issue description

Chrome Version       : 61.0.3163.25 (Official Build) dev (64-bit)
URLs (if applicable) : http://localhost:3000/
Other browsers tested: Safari, Firefox
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
     Safari: OK Version 10.1.1 (12603.2.4)
    Firefox: OK Developer Edition 55.0b14 (64-bit)
         IE: N/A

What steps will reproduce the problem?
(1) Open the URL
(2) Open the JavaScript Console
(3) Make sure console filter enables warnings

What is the expected result?
No warnings

What happens instead?
A warning in the console saying, "Chrome is blocking ads on this site because this site tends to show ads that interrupt, distract, or prevent user control. You should fix the issues as soon as possible and submit your site for another review. Learn more at https://www.chromestatus.com/feature/5738264052891648"

Please provide any additional information below. Attach a screenshot if
possible.
I'm testing an Ionic app with a Meteor backend, and when I went to change some colors of the theme today, I saw the warning for the first time.  My app doesn't use ads, but I think Chrome is wary of localhost because anything can run there.  I think this warning shouldn't show up since it's context sensitive.  By that, I mean not every instance of localhost shows ads.  It's not a real website.  I think this warning should never display for localhost.
 
Status: Fixed (was: Unconfirmed)
This was the result of a bad experiment config push, it should be fixed with a new config (which should occur with a restart).

Please update the bug if a restart does not fix the issue.
Thank you, restarting fixed it.

Sign in to add a comment